Update to latest upstream #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't assume, that the default background-color is white. My default background-color is dark, which makes the documentation hardly readable: https://i.imgur.com/xN0UjWz.png The reason is the transparency of the existing color (rgba(252, 248, 244, 0.45);) Fixed by removing the transparency.
* Added codeRepr and dumpCode to the macros module. This allows those writing macros to write examples, get the code to generate the AST for that example, and then modify that code to be dynamic with the macro function.
* fix allocator corruption for large sizes * allow large chunks to coalesce and added test case * use correct constants in MaxBigChunkSize
Add string overload for parseXml
Fix background-color in nimdoc.cfg
This heading is for the automatically generated list of issues fixed.
`basic2d` and `basic3d` has been moved to nimble packages
Allow searching for "rename file" in documentation
Related to #7417
|
I think we'll be better off rebasing against devel instead of merging it. This will lead to a little bit of inconvenience from time to time (you'll have to use force pushes and fetches when migrating to a new version), but the benefit is that our patches will be much easier to review (they will always appear as the last few commits following a certain devel HEAD). Right now in particular, our patches got squash-merged in the Nim repo, so we can just force-push Nim's devel over the nimbus branch. |
* fix deprecation warnings in asyncmacro and htmlgen * removed todo
…mit FD allocation (#7564)
We accept a new environment variable, NIMTEST_COLOR, which override the effect of NIMTEST_NO_COLOR. The environment variable, NIMTEST_COLOR, can be 'never' or 'always', which set the color output to false or true, respectively.
* Add column number to instantiation info Instantiation info left out column number for no good reason. This adds it in as the third element of the tuple. * Fix test that failed and added change to changelog An assertion test failed because it was declaring a type that was expected to be populated by instantiationInfo with the old signature. Also added the changes to the changelog as it is a breaking change.
|
Furthermore, our branch is actually called |
zah
pushed a commit
that referenced
this pull request
Jun 7, 2018
updating my fork with the head repo
stefantalpalaru
pushed a commit
that referenced
this pull request
May 28, 2019
Getting the latest from nim-lang
etan-status
pushed a commit
that referenced
this pull request
Apr 10, 2023
tlsEmulation:on under NetBSD-10Beta and NetBSD-current produces an executable which crashes immediately as follows: Core was generated by `koch'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000000047b4c2 in nimZeroMem () (gdb) bt #0 0x000000000047b4c2 in nimZeroMem () #1 0x00000000004897b2 in threadVarAlloc__system_2162 () #2 0x000000000048980e in initThreadVarsEmulation () #3 0x0000000000489848 in PreMain () #4 0x000000000048986a in NimMain () nim-lang#5 0x00000000004898a9 in main () I can't speak about the other BSDs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.