Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

misc TODO #121

Open
1 task
timotheecour opened this issue Apr 23, 2020 · 12 comments
Open
1 task

misc TODO #121

timotheecour opened this issue Apr 23, 2020 · 12 comments

Comments

@timotheecour
Copy link
Owner

  • # xxx: fix this pre-existing bug causing SuccessX error messages to lie
@timotheecour
Copy link
Owner Author

@timotheecour
Copy link
Owner Author

timotheecour commented Apr 24, 2020

@timotheecour
Copy link
Owner Author

mv changelog, see nim-lang#14098 (comment)

@timotheecour
Copy link
Owner Author

timotheecour commented May 14, 2020

@timotheecour
Copy link
Owner Author

timotheecour commented May 22, 2020

@timotheecour
Copy link
Owner Author

@timotheecour
Copy link
Owner Author

check whether NRVO suppression impacts performance fixes #14126 [backport:1.2] by Araq · Pull Request #14390 · nim-lang/Nim

@timotheecour
Copy link
Owner Author

@timotheecour
Copy link
Owner Author

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)

@timotheecour
Copy link
Owner Author

nim-lang@70c289c
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"

@timotheecour
Copy link
Owner Author

document gotcha
nim-lang#16182 (comment)

indeed. also noticed in nim-lang#13448. It's so bad that newSeqOfCap should come with a performance warning in its doc comment explaining the newSeqOfCap(n) + seq.add(elem) anti-pattern. This isn't specific to nim.

@juancarlospaco
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants