martinfreedman
martinfreedman
@SleeplessByte For the test tooling that supports it, it is quite clear that this is a condition for a test to not time out and that a timeout is a...
@SaschaMann example added to Readme
I am happy to change to @ErikSchierboom 's suggestion using `scenarios`and `tests.toml`. IMV the key point is that these are performance constrained tests and this needs to be captured as...
I think "performance" scenario best captures what is being tested, whereas "timeout" states how to do that and can be a function of different languages and test frameworks. "Inefficient" and...
> I don't like `performance` for this. `performance` suggests to me that it could also be about optimising the implementation in the language to make it faster without changing the...
I do not follow this since, both scenarios (if there are really two , not sure) require _same_ handling in a test, in the case of F# & C# by...
Given the point that @SaschaMann made namely " whereas the exercises you mention are primarily about algorithmic optimisations." how about **Optimise**?
I like what @BethanyG implies "Efficient" better than "Optimise" (and especially not "Optimize"). Or maybe "TimeEfficiency" as that is the specific issue I am addressing and offering a solution for....
@ErikSchierboom you mean "time-optimise" or "optimise-time". Most of us are not from the USA, why should we have the imposition of USA spelling?
I like the idea that this exercise be fully correct. However I would suggest that you make a more advanced version of this as a new exercise? Similar to how...