-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Closures do not work yet #123
Comments
Seem to be pretty stable now. |
krux02
pushed a commit
to krux02/Nim
that referenced
this issue
Jan 11, 2022
128: Remove Atlas r=alaviss a=juancarlospaco <!-- ## Tips for pull requests * use chat, discussions, etc... to refine an idea for big and/or impactful changes * open them relatively early in draft mode and get regular feedback * add notes for reviewers and yourself as you go, so it's easy to maintain context * refine the pull request message over time --> <!-- ## Finalizing a PR: ### title: * reads like a short changelog line ### body: * describe the current behaviour * describe why this particular approach * if it's breaking, migration steps * note any follow-on work ### content: * leave code better than you found it, add docs, tests, etc --> <!-- * note any issues that this fixes entirely * use `fixes nim-lang#123 .` to auto-close issues --> ### Remove Atlas * Remove Atlas. Co-authored-by: Juan Carlos <juancarlospaco@gmail.com>
krux02
pushed a commit
to krux02/Nim
that referenced
this issue
Jan 11, 2022
124: store extra metadata in release archives r=alaviss a=alaviss This allows koch to fill in commit/commit date data when compiling the compiler from a source archive. A prerequisite for nightlies. We are getting deep into the `niminst` is compiler-only territory with this. I hope that in the future I can make nim-lang#123 happen and consolidate everything into koch. Co-authored-by: Leorize <leorize+oss@disroot.org>
Clyybber
pushed a commit
to Clyybber/Nim
that referenced
this issue
Feb 9, 2022
152: put links 'for developers' on the top r=saem a=haxscramper In documentation overview, put links 'for developers' on the top of the page <!-- ## Tips for pull requests * use chat, discussions, etc... to refine an idea for big and/or impactful changes * open them relatively early in draft mode and get regular feedback * add notes for reviewers and yourself as you go, so it's easy to maintain context * refine the pull request message over time --> <!-- ## Finalizing a PR: ### title: * reads like a short changelog line ### body: * describe the current behaviour * describe why this particular approach * if it's breaking, migration steps * note any follow-on work ### content: * leave code better than you found it, add docs, tests, etc --> <!-- * note any issues that this fixes entirely * use `fixes nim-lang#123 .` to auto-close issues --> Co-authored-by: haxscramper <haxscramper@gmail.com>
Clyybber
pushed a commit
to Clyybber/Nim
that referenced
this issue
Feb 9, 2022
165: koch: generate zstd archives by default r=alaviss a=alaviss Zstandard is a fast compression algorithm with ratio rivaling that of XZ. Emperical testing on my Ryzen 5 3600 resulted in a massive improvement in compression and decompression speed, in particular: - Zstd is 13% faster than XZ for compression. - Zstd is 88% faster than XZ for decompression. - Zstd archive is 6% larger than XZ archive. All tests are done on an unix binary tarball generated by: ```sh ./koch.py unixrelease --format:tar ``` With this change we will be trading off a small amount of space for a massive improvement in compression and decompression time. <!-- ## Tips for pull requests * use chat, discussions, etc... to refine an idea for big and/or impactful changes * open them relatively early in draft mode and get regular feedback * add notes for reviewers and yourself as you go, so it's easy to maintain context * refine the pull request message over time --> <!-- ## Finalizing a PR: ### title: * reads like a short changelog line ### body: * describe the current behaviour * describe why this particular approach * if it's breaking, migration steps * note any follow-on work ### content: * leave code better than you found it, add docs, tests, etc --> <!-- * note any issues that this fixes entirely * use `fixes nim-lang#123 .` to auto-close issues --> Co-authored-by: Leorize <leorize+oss@disroot.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current implementation of closures is broken and needs to be fixed.
The text was updated successfully, but these errors were encountered: