Edit - Code Golf Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Title*

Body*

There are 4 regular polygons that we can construct using ASCII art:

<pre>
 . . .
 . . . . . . .
 . . . . . . . . . . . . .
 . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
 . . . . . . .
 . . .
</pre>

That is, a triangle, a square, a hexagon and an octagon.

Your task is to take two inputs and produce the corresponding ASCII art polygon.

## Input

The two inputs will be:

- A string/list of printable ASCII characters (i.e. with code points in the range \33ドル\$ (`!`) to \126ドル\$ (`~`)
- An indicator as to which polygon you should output. This indicator can be any \4ドル\$ distinct and consistent values (e.g. `1234`, `ABCD`, etc.), but each must be only one character long, to avoid any exploitation of this input.

The string will be a perfect fit for the polygon, meaning that, if the shape to be outputted is:

- A triangle, then the length of the string will be a [triangular number](http://oeis.org/A000217)
- A square, then the length of the string will be a [square number](http://oeis.org/A000290)
- A hexagon, then the length of the string will be a [centered hexagonal number](http://oeis.org/A003215)
- An octagon, then the length of the string will be an [octo number](http://oeis.org/A079273)

The string may have repeated characters, but will always fit the appropriate lengths for the given shape/sequence, so there is no need to worry about too many/few characters.

## Output

You should output a shape, indicated by the second input, in the format shown at the top of the challenge with the `.` replaced with the characters in the inputted string. Each character must be separated by a single space, and leading/trailing whitespace is acceptable, so long as the shape is preserved. The characters may be used in any order, but each character in the string must only appear once. For example, for a hexagon using `ABCDABC`, the following are valid:

<pre>
 A B B A
C D A A B C
 B C D C
</pre>

as each character from the string is used once. However,

<pre>
 A A A B AD
A A A A B C ABC
 A A C A BC
</pre>

are not valid (the first only has `A`, the second doesn't have a `D` and the third doesn't have spaces between characters).

This is [tag:code-golf] so the shortest code in *bytes* wins

## Test cases

These test cases use `T`, `S`, `H` and `O` to indicate which shape the output should be in. The string of characters is on the first line and the indicator on the second

```
i1+K8{^wsW
O

 i 1
+ K 8
{ ^ w
 s W


,r1~vi4l{W@+r<vzP;mq>:8gJcgg$j`$RFhDV
H

 , r 1 ~
 v i 4 l {
 W @ + r < v
z P ; m q > :
 8 g J c g g
 $ j ` $ R
 F h D V


0J++
S

0 J
+ +


Kn[Vyj
T

 K
 n [
V y j


#5~m
S

# 5
~ m


'*g(AUFV~Ou2n=172s'|S11q&j=+#
O

 ' * g
 ( A U F
V ~ O u 2
n = 1 7 2
s ' | S 1
 1 q & j
 = + #

If this is an answer to a challenge…

…Be sure to follow the challenge specification. However, please refrain from exploiting obvious loopholes. Answers abusing any of the standard loopholes are considered invalid. If you think a specification is unclear or underspecified, comment on the question instead.
…Try to optimize your score. For instance, answers to code-golf challenges should attempt to be as short as possible. You can always include a readable version of the code in addition to the competitive one. Explanations of your answer make it more interesting to read and are very much encouraged.
…Include a short header which indicates the language(s) of your code and its score, as defined by the challenge.

More generally…

…Please make sure to answer the question and provide sufficient detail.
…Avoid asking for help, clarification or responding to other answers (use comments instead).

Draft saved

Draft discarded