Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Challenges Q&A Sandbox Meta
Meta
Posts Tags Edits
Ask Question

Comments on Default Rules: Code Golf I/O

Parent

Default Rules: Code Golf I/O

+8
−0

What input/output methods do you think should be allowed/disallowed while code golfing on this site? What guidelines for input/output methods do you think should be in place?

One method per answer, please. Vote up/down according to if you believe the given method should be allowed.

default-rules
posted over 3 years ago
user card
Quintec‭
2306 reputation 17 46 242 48
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+7
−0

Functions may take multiple arguments with currying

For some languages like Haskell this is almost a necessity, as only one-argument functions exist and multi-argument functions are implemented with currying. (You might take a list or tuple of the values but this isn't the natural way to do multi-arg functions in Haskell.)

The same thing should be allowed for languages which do have proper multi-argument functions. In JavaScript, one might want to use f=a=>b=>... and call f(a)(b) instead of using f=(a,b)=>... and calling f(a, b).

posted over 3 years ago
user card
AndrewTheCodegolfer‭
1700 reputation 8 30 166 26
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

I'm not sure this needs to be said; it's a pretty obvious rule, but it might be good to have it writt... (2 comments)
I'm not sure this needs to be said; it's a pretty obvious rule, but it might be good to have it writt...
user‭ wrote over 3 years ago
copy link

I'm not sure this needs to be said; it's a pretty obvious rule, but it might be good to have it written explicitly.

AndrewTheCodegolfer‭ wrote over 3 years ago
copy link

This is intended to be a "the" of the possible input and output formats. Sure, it's obvious, but it has to be marked anyway so that there is a solid basis for it instead of just unspoken social contract.