Rosetta Code:Village Pump: Difference between revisions
(→Home: Recent Changes broadcast) |
(username removed) (Test) |
||
(88 intermediate revisions by 28 users not shown) | |||
Line 1: | Line 1: | ||
⚫ | |||
==Home== |
|||
|topic=Title |
|||
⚫ | This is the |
||
|summary=Summary of the topic |
|||
*{{vp|Recent Changes broadcast}} |
|||
}}</nowiki></pre>substituting your topic title for "Title" and a summary for "Summary of the topic". |
|||
*{{vp|Language template enhancements}} |
|||
{{#ask:[[Is village pump topic::true]] |
|||
*{{vp|Works with against libheader}} Which is the "real" difference? |
|||
|?Summary |
|||
*{{vp|Enable Mediawiki API Edit}} |
|||
|?Modification date |
|||
*{{vp|Syntax_Highlighting}} |
|||
|format=broadtable |
|||
*{{vp|Bash_examples}} |
|||
|limit=20 |
|||
*{{vp|Task creation process discussion}} |
|||
|order=desc |
|||
*{{vp|Foldable output}}. Request for ability to hide lines of output |
|||
|sort=Modification date |
|||
*{{vp|Examples needing attention}} |
|||
|searchlabel=Older topics... |
|||
*{{vp|Admin assistance request}} |
|||
|offset=0 |
|||
*{{vp|Running the programs}} |
|||
}} |
|||
*{{vp|News Channel}} |
|||
*{{vp|Less Than X Examples}} |
|||
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). |
|||
*{{vp|Income}} |
|||
*{{vp|Tex and Math}} |
|||
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. |
|||
*{{vp|Image uploads}} |
|||
*{{vp|Screwed pages}} |
|||
== create statically-validated API == |
|||
<br/> |
|||
This is a challenge proposed by Tony Morris here: |
|||
blog.tmorris.net/posts/understanding-practical-api-design-static-typing-and-functional-programming/ |
|||
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: |
|||
github.com/tismith/tictactoe-haskell/blob/master/Tictactoe.hs |
|||
Further discussion and links to some other solutions: |
|||
github.com/data61/fp-course/blob/master/projects/TicTacToe/TicTacToe.markdown |
Latest revision as of 18:10, 21 November 2023
This is the 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
{{Vptopic |topic=Title |summary=Summary of the topic }}
substituting your topic title for "Title" and a summary for "Summary of the topic".
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
This is a challenge proposed by Tony Morris here:
blog.tmorris.net/posts/understanding-practical-api-design-static-typing-and-functional-programming/
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:
github.com/tismith/tictactoe-haskell/blob/master/Tictactoe.hs
Further discussion and links to some other solutions:
github.com/data61/fp-course/blob/master/projects/TicTacToe/TicTacToe.markdown