Timeline for Floating over the integers
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2019 at 3:01 | history | tweeted | twitter.com/StackCodeGolf/status/1111463333327224832 | ||
| Mar 4, 2019 at 3:09 | comment | added | Jo King | I don't mind switching my code to score in bytes if you want | |
| Mar 4, 2019 at 1:50 | comment | added | don bright | @EriktheOutgolfer yeah i see what you mean... next time ill probably do bytes | |
| Mar 4, 2019 at 1:46 | vote | accept | don bright | ||
| Feb 27, 2019 at 10:42 | comment | added | Erik the Outgolfer | @donbright Alright, your call. BTW it's not that code golf is strictly scored in bytes, it was in characters for a long time many years ago, it's just that I recommended scoring in bytes based on my personal experience. | |
| Feb 27, 2019 at 7:29 | answer | added | Kevin Cruijssen | timeline score: 1 | |
| Feb 26, 2019 at 23:56 | comment | added | don bright | @EriktheOutgolfer sorry, Jo King already used this in their perl answer so I am kind of stuck... . For now i changed it to "Code Gofl" to indicate its not technically Code Golf. | |
| Feb 26, 2019 at 23:53 | history | edited | don bright | CC BY-SA 4.0 |
update as listed
|
| Feb 26, 2019 at 23:43 | comment | added | don bright | @Sara-J order does not matter. Updated, thanks. | |
| Feb 26, 2019 at 23:14 | comment | added | Sara J |
Do the numbers have to be output in order? Or would your example be valid if it output, for example, [16777223,16777221,16777219,16777217]?
|
|
| Feb 26, 2019 at 20:45 | comment | added | Erik the Outgolfer | @donbright I recommend scoring in bytes. The reason is that, otherwise, the full code in ASCII-only golfing languages (such as CJam or Pyth) can be compressed in a unicode string that will unpack to the ASCII-only code, therefore saving characters, but not bytes. Furthermore, the byte is the actual unit of digital data storage, while "character" is a term that depends on the encoding the solution uses, and one character can even take up 6 bytes, for example. This is how the "packing" mentioned before worked before we changed the default scoring method for code-golf to the byte count. | |
| Feb 26, 2019 at 16:51 | answer | added | Stephen | timeline score: 1 | |
| Feb 26, 2019 at 16:32 | answer | added | Gymhgy | timeline score: 1 | |
| Feb 26, 2019 at 14:17 | answer | added | Kevin Cruijssen | timeline score: 2 | |
| Feb 26, 2019 at 14:07 | answer | added | Kirill L. | timeline score: 2 | |
| Feb 26, 2019 at 11:09 | answer | added | nwellnhof | timeline score: 3 | |
| Feb 26, 2019 at 9:03 | comment | added | tsh | @xnor I don't think it should include this just because most language use IEEE754 floating point numbers. Other form of floating point numbers should be allowed although I don't know one. | |
| Feb 26, 2019 at 8:55 | answer | added | tsh | timeline score: 2 | |
| Feb 26, 2019 at 6:17 | comment | added | xnor | Could you please remind us how a positive integer is represented as a float? I know I can look it up, but challenges specifications should be self-contained and it would save readers the time. | |
| Feb 26, 2019 at 6:15 | comment | added | Gymhgy | Do we use single precision floating point or double? | |
| Feb 26, 2019 at 5:28 | comment | added | don bright | i just love unicode? | |
| Feb 26, 2019 at 5:27 | answer | added | DLosc | timeline score: 1 | |
| Feb 26, 2019 at 5:26 | comment | added | Jo King |
Smallest number of characters wins I think you mean bytes. If not, is there a reason you're using characters?
|
|
| Feb 26, 2019 at 5:26 | answer | added | Jo King | timeline score: 3 | |
| Feb 26, 2019 at 5:09 | history | asked | don bright | CC BY-SA 4.0 |