• Test error handling/boundary conditions/sanitizer results as well (would be reported as a failure for that round like the tech empower rounds) • Final score would be aggregate across a several operating systems, perhaps even CPU architectures.
-
-
-
Plus 1. Needs to be done across multiple OS'es and CPU types to get a good idea. Probably with multiple core counts as well from 1 to 128 to get an idea of how solutions scale as well.
- 5 more replies
New conversation -
-
-
It's not about programming languages, but instead, techniques.
-
Could you unpack that a bit? Or more precisely, how would that manifest as a concrete change to the existing Benchmark Game?
- 2 more replies
New conversation -
-
-
I wouldn't let people keep optimizing the same benchmarks. I'd introduce new tasks, and the game would be how quickly they could make efficient code.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Somehow add an idomaticness score. I like the scores on 'Completely Unscientific Benchmarks'.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Stats on the time taken to clean build each answer.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For one: allow implementations of new languages like Nim instead of refusing to add them for some reason.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Maybe do the benchmark game but all entries have to be in wasm?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.