Talk:Teacup rim text

From Rosetta Code

Limiting output

It seems that there could be a lot of output generated - maybe alter the wording to ask for example words and maybe summaries of words found of particular lengths? --Paddy3118 (talk) 20:47, 4 August 2019 (UTC)

I think it would be better to use a common (available) dictionary (so we could compare results).     -- Gerard Schildberger (talk) 22:35, 4 August 2019 (UTC)
I shall specify the wordlist and be specific about the result set. Axtens (talk) 01:10, 5 August 2019 (UTC)
Okay that's done. How do I tell the Perl6 contributor to abbreviate his output? Axtens (talk) 03:40, 5 August 2019 (UTC)


A good task description specifies a problem rather than a procedure

The real task/problem here is to identify and display a subset of words (in a given lexicon) that are 'circular' in the sense which you describe.

The current formulation (para 3) is the narration of a procedure, rather than the statement of a problem or task, and is perhaps not yet quite consistent with the Rosetta Code goal (see the landing page) of aiding a person with a grounding in one approach to a problem in learning another.

(Not all languages or techniques of code composition are built around a notion of 'procedure'. In the traditions of Lisp, Scheme, Racket, ML, Haskell etc, the process of evaluation is central).

Usually better to just state the problem, and leave the technique of its solution to the contributors. Hout (talk) 12:04, 5 August 2019 (UTC)