I'm working on modernizing Rosetta Code's infrastructure. Starting with communications. Please accept this time-limited open invite to RC's Slack.. --Michael Mol (talk) 20:59, 30 May 2020 (UTC)

Rosetta Code:Village Pump

From Rosetta Code
(Redirected from Talk:Rosetta Code)
This is the new place for Rosetta Code community activity. To start a new "thread", just append a "/" to the end of the URL of this page and give your thread a short title. On the new topic page add
|summary=Summary of the topic
substituting your topic title for "Title" and a summary for "Summary of the topic".
 SummaryModification dateThis property is a special property in this wiki.
Village Pump/Discouraging approachesThe goals of Rosetta Code, and responding to code which we disapprove of.2 April 2021 07:30:47
Village Pump/Phix geshi filenew syntax file31 March 2021 13:49:25
Village Pump/Syntax highlightingDiscuss issues related to the Syntax Highlighting system here. The old page got huge, and it became hard to discern what problems were current.8 March 2021 10:38:54
Village Pump/Old draft tasksDiscussion on what to do about draft tasks which don't seem to be getting attention25 December 2020 06:49:45
Village Pump/hopl.murdoch.edu.au UnavailableBroken links to HOPL29 November 2020 22:34:11
Village Pump/Unlisted tasksSeveral tasks are not showing up in the site listings31 July 2020 10:25:37
Village Pump/Please appoint more Moderators!The number of active bureaucrats / moderators appears to be 1. 2!24 March 2020 00:53:48
Village Pump/https links in emailUse https: rather than http: links in all notification emails from rosetta code.19 March 2020 17:23:05
Village Pump/Add link anchors to Language Category pagesSuggestion to add Anchors to specific language examples17 January 2020 02:27:19
Village Pump/RC thinks cookies are disabled on ChromeSelf-explanatory. I had to log in on Firefox just to file this page.16 September 2019 00:23:20
Village Pump/Email protection in codeSometimes parts of the source code is replaced with "email protected".16 July 2019 16:42:59
Village Pump/RC extraction Tool and TaskExtracting material from RC specific to one language10 May 2019 21:21:58
Village Pump/tasks descriptions onlyHow to get a list of programming tasks *without* solutions30 January 2019 16:43:53
Village Pump/Did I implement this new task correctlyRE: Implementing new tasks24 August 2017 22:01:42
Village Pump/Category IntersectionsFinding pages in the intersection of two or more categories12 June 2017 20:26:26
Village Pump/Repairing invisible formulae58 tasks still have formulae that have accidentally been made invisible to most browsers, mostly during a campaign of under-tested cosmetic edits over the last six months. Volunteer repair work welcome. The full list is at http://rosettacode.org/wiki/User_talk:Hout24 September 2016 11:38:02
Village Pump/CSS problem with Progress languageThe CSS for the Chamelion Theme has a conflicting CSS directive9 July 2016 01:43:47
Village Pump/Adding transclusion pluginSuggestion to add an existing mediawiki plugin, Transclusion, to address other village pump topics5 December 2015 06:03:51
Village Pump/Sort popular pump pagesA Python implementation of pump sorting code.25 October 2015 06:09:18
Village Pump/SMW Examples by language and conceptDiscussion and planning for using SMW to organize/tag examples by language and concepts demonstrated by that example7 October 2015 20:56:14
Older topics...

Hi, sorry to post this here but I don't know a better place. I wanted to create a new proposed task "Create statically-validated API" but it's impossible to create a page without solving a captcha, and the browser I use doesn't show the captcha (I was able to create this account using a phone browser, but that's no good for entering much text or code). Maybe someone can move it to the right place? (Added: I also had to de-link the urls to bypass the captcha).

By the way I find this site a huge pain to use because of the captchas. Email verification for account creation is likely to be enough.

create statically-validated API[edit]

This is a challenge proposed by Tony Morris here:


It is only for statically-typed languages and the challenge is to implement a Tic-tac-toe API that supports operations like starting a game, making a move, and seeing who won, where invalid arguments (such as asking who won an unfinished game) are rejected by the compiler as compile-time type errors. So it is mostly a test of how expressive the language's type system is.

A Haskell solution (not by me) is here:


Further discussion and links to some other solutions: