Skip to main content

Timeline for Sandbox for Proposed Challenges

Current License: CC BY-SA 4.0

12 events
when toggle format what by license comment
Mar 28, 2020 at 7:18 history undeleted CommunityBot
Mar 27, 2020 at 6:51 history deleted CommunityBot via Vote
Mar 27, 2020 at 6:43 comment added user92069 @Bubbler Ahh, the challenge is just about checking whether the square of the integral part is close to the the decimal part. Should I post it?
Mar 27, 2020 at 6:40 history edited user92069 CC BY-SA 4.0
added 244 characters in body
Mar 27, 2020 at 6:39 comment added Bubbler I don't see how restricted source will fit here. Btw, a big truthy test case: 50.2501
Mar 27, 2020 at 6:35 history edited user92069 CC BY-SA 4.0
added 244 characters in body
Mar 27, 2020 at 6:25 history edited user92069 CC BY-SA 4.0
added 170 characters in body
Mar 27, 2020 at 6:13 comment added Bubbler 4) For truthy/falsy, it currently reads like I can output the input as-is and say "the program's output format is a RRE number for truthy, a non-RRE number for falsy". What I use is "truthy/falsy following the language's convention, or exactly one value for truthy and another for falsy".
Mar 27, 2020 at 6:07 comment added Bubbler 1) Rounding 4.666... to two decimal places gives 4.67. 2) Floating-point numbers are always subject to precision issues. I think it's best to let the programs take a string representation as input, and state that "programs are allowed to give wrong output if the absolute difference is very close to 2". 3) If the integral part is 0, the algorithm will invoke division by 0. Is handling it part of the challenge?
Mar 27, 2020 at 5:13 history edited user92069 CC BY-SA 4.0
added 181 characters in body
Mar 27, 2020 at 5:06 history edited user92069 CC BY-SA 4.0
added 203 characters in body
Mar 27, 2020 at 5:01 history answered user92069 CC BY-SA 4.0