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 »
Meta

Comments on Default minimum required precision and supported size for inputs

Post

Default minimum required precision and supported size for inputs

+1
−0

For challenges that require a input, what is the maximum a solution has to support, if not further specified by the challenge author?

Lets say the input is a string, how long a string has to be accepted? I assume it isn't infinite since that would eliminate most programming languages and all real world implementations of all programming languages. Same for other arrays/lists.

For integers, is there a maximum value a solution has to support?

For real numbers, is there a maximum precision or a minimum error that needs to be supported?

For challenges that require a growing output, like this one, what is the maximum amount a solution has to output before it fails?

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?

2 comment threads

One proposal per answer (7 comments)
Can't accept edit suggestion (2 comments)
One proposal per answer
trichoplax‭ wrote about 1 year ago

It might be easier to see community consensus if each proposed rule is posted in its own answer to allow separate voting. This will then be similar to the other Meta questions tagged "default-rules".

H_H‭ wrote about 1 year ago

Should i split the question to ask for each rule separately?

trichoplax‭ wrote about 1 year ago · edited about 1 year ago

I was commenting as a hint to answerers. I don't see a problem with several related rules being discussed under one question - that's similar to how the other "default-rules" questions work.

The concepts you have listed in the question are all very closely related, so I like them being in one question. I just meant that if an answer gives a rule for string length and a rule for number of decimal places, then someone may agree with one rule and disagree with the other, and voting cannot express that unless the 2 rules are in separate answers.

H_H‭ wrote about 1 year ago · edited about 1 year ago

Yes. But if we split answers, wouldn't it make sense to also split the question? One question for Integer size, one for list lengths and one for "floating point" accuracy?

trichoplax‭ wrote about 1 year ago · edited about 1 year ago

Similarly if an answer gives 2 rules for string length, they cannot be separately voted on. For example, if someone says "string inputs only have to be supported up to N characters" but also says "for language X it's M characters" then someone may agree with the general rule but not with the exception for language X.

trichoplax‭ wrote about 1 year ago

So I think splitting answers will be needed even if this is split into more questions. I don't personally see a need to split this question, but I don't see a problem with splitting it either.

trichoplax‭ wrote about 1 year ago

One thought which makes me lean towards keeping it a single question:

The line between different types is not always clear. Some languages have floating point for non-integer values, other languages have fixed point, or an arbitrary precision decimal or rational type. Since there might be some overlap there may be an advantage to keeping all the discussion in one place.