Open timotheecour opened 4 years ago
eg use case: see https://github.com/nim-lang/Nim/pull/14102/files, see this comment for justification: https://github.com/nim-lang/Nim/pull/14102#discussion_r414332876
mv changelog, see https://github.com/nim-lang/Nim/pull/14098#issuecomment-619028912
Edited: They are already quoted https://github.com/nim-lang/Nim/pull/14992/files
redo profiling after specialize genericReset by Araq · Pull Request #14398 · nim-lang/Nim
check whether NRVO suppression impacts performance fixes #14126 [backport:1.2] by Araq · Pull Request #14390 · nim-lang/Nim
TODO leftover from no more code duplication bw liMessage and rawMessage + several bug fixes by timotheecour · Pull Request #14415 · nim-lang/Nim
I encountered other bugs while fixing this but best to keep this one as mostly refactoring, next one will fix bugs I've encountered (at least they'll only need to be fixed in 1 place)
https://github.com/nim-lang/Nim/pull/16151/commits/70c289c46121a5182a34261177baffb8909584d6 testament/testament.nim
revert formatting change Expected: {..} Gotten{..} from this PR
else:
maybeStyledEcho fgYellow, "Expected:"
maybeStyledEcho styleBright, "{", expected, "}\n"
maybeStyledEcho fgYellow, "Gotten:"
maybeStyledEcho styleBright, "{", given, "}\n"
document gotcha https://github.com/nim-lang/Nim/pull/16182#issuecomment-735646532
indeed. also noticed in https://github.com/nim-lang/Nim/pull/13448. It's so bad that
newSeqOfCap
should come with a performance warning in its doc comment explaining thenewSeqOfCap(n) + seq.add(elem)
anti-pattern. This isn't specific to nim.
SuccessX
error messages to lie