Timeline for What is our consensus on floating point issues?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9, 2021 at 21:16 | comment | added | Rosie F | Good point. If some implementation of some algorithm is poor (inaccurate) because it used poor tools (floating-point), then it is no mitigation to say that using them inevitably risks poor results. The answerer should instead consider implementing that same algorithm using better tools. Or a different algorithm. | |
| Dec 4, 2020 at 13:35 | comment | added | rydwolf | @WheatWizard I guess a better way to have put it would be "I don't agree with this for all challenges", but I do think these are useful points to bring up. | |
| Dec 4, 2020 at 10:30 | history | made wiki | Post Made Community Wiki by Wheat WizardMod | ||
| Dec 4, 2020 at 10:29 | comment | added | Wheat Wizard Mod | Maybe don't post answers you don't agree with. This is a discussion not a poll, sharing your honest ideas is much more valuable, and if there are people who support this view point one of them will surely make their case. | |
| Dec 3, 2020 at 23:55 | comment | added | rydwolf | I don't necessarily agree with this, but I do think these are valid points against it. | |
| Dec 3, 2020 at 23:53 | history | answered | rydwolf | CC BY-SA 4.0 |