summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Fix #21595 (#22233)Juan Carlos2023-07-071-2/+1
| | | | | * . * Fix #21595
* Tolerate markup errors for doc comments (#19607) (#22235)Andrey Makarov2023-07-072-5/+17
| | | | | | | | | | | | | | | | | Follow-up to #21576 (for solving #19607). 1) errors in Markdown mode for `.nim` doc comments are reported with red color but allow to generate `.html` with the comment represented by literate block (monospaced text). We suppose that it's what people want for (supposedly) small doc comments. And this behavior is also a bit more Markdown-ish in the sense that Markdown generally does not have the concept of parsing error. - However, for standalone `.md` it's **not** applied because for large files the consequences are way bigger. (In {.doctype: rst.} mode the behavior is the same as before -- report the error and stop.) In future, when our parser can handle Markdown without errors according to the spec, this code will most probably be not needed.
* Fix #21401 (#22232)Juan Carlos2023-07-071-0/+8
|
* fixes #22175 (#22229)Andreas Rumpf2023-07-062-2/+17
|
* alternative to #22219; adds a pointer wrapper for T destructor (#22225)ringabout2023-07-062-6/+53
| | | | | | | | | | | | | | | * alternative to #22219; adds a pointer wrapper for T destructor * clean up and add comments * Update compiler/ccgtypes.nim * tidy up * fixes comments * fixes cpp * fixes cpp
* Fix concepts with doc comments (#22228)Jake Leahy2023-07-062-1/+14
| | | | | | | | | | | | | | | * Add testcase This tries to use a concept with a doc comment which currently leads to a segfault * Ignore nil nodes which happen when there are doc comments in new style concept This was done instead of semming the comments since `semConceptDecl` says it only supports lists of actual statements * Go with alternative fix: Sem comments but ignore them Since `nil` could mean anything it is best to not silently ignore it (In case another nil problem happens in future Also fix test case so it isn't an infinite loop
* fixes #22132; hoisted openArray params result in erroneous code (#22224)ringabout2023-07-052-1/+22
|
* fixes #22138 (#22221)Andreas Rumpf2023-07-042-2/+27
|
* add a test case for #22190 in case of regression (#22217)ringabout2023-07-041-0/+21
|
* fixes #22212; Compile error when running a Nimscript that compares se… ↵ringabout2023-07-032-4/+16
| | | | | (#22213) fixes #22212; Compile error when running a Nimscript that compares seq with switch("mm", "arc")
* fixes #22208; Ambiguous error when import modules with same names but… ↵ringabout2023-07-036-4/+13
| | | | | (#22211) fixes #22208; Ambiguous error when import modules with same names but different aliases
* clean up the documentation (#22196)ringabout2023-07-0212-34/+28
|
* fixes #22197; Distinct ref objects + destructor cause C++ codegen error (#22207)ringabout2023-07-022-1/+34
|
* fixes #22200 (#22206)Andreas Rumpf2023-07-021-0/+4
| | | | | * fixes #22200 * typo
* Bisect Bugs (#22157)Juan Carlos2023-07-011-0/+20
| | | | | * Add Git bisect like for bug repro code on issue comments against Nim versions >1.0 * Add Git bisect like for bug repro code on issue comments against Nim versions >1.0 * Add Git bisect like for bug repro code on issue comments against Nim versions >1.0
* Tidy contributing.md: format cmd (#22204)心夏❤v2023-07-011-2/+2
|
* reset macrocache after each script evaluation (#22195)Juan M Gómez2023-06-302-1/+31
|
* fix controlflow test (#22194)Jacek Sieka2023-06-301-1/+1
| | | the function actually returns
* v2.0: changelog improvements (#22192)Andreas Rumpf2023-06-302-482/+810
| | | | | | | * changelog improvements * changelog that people want to actually read * improvements
* fix nested call regression in generic bodies (#22189)metagn2023-06-292-0/+31
| | | fixes #22187
* alternative to #22183; nimscript shares the same compileTime sym with VM ↵ringabout2023-06-293-1/+21
| | | | (#22184)
* fixes #19101; zero initialization union casts (#22185)ringabout2023-06-296-13/+38
| | | | | | | * zero initialization union casts * cleans up and adds a test case for #19101 * uses nimZeroMem
* Don't throw errors on RST tables in Markdown and RstMarkdown modes (#22165)Andrey Makarov2023-06-282-15/+62
| | | | | | | | | | | | | | | | | | | | | * Don't throw errors on RST tables in Markdown and RstMarkdown modes Additions to RST simple tables (#19859) made their parsing more restrictive, which can introduce problems with of some old nimforum posts, which have tables with sloppily aligned columns (like this one: https://github.com/nim-lang/nimforum/issues/330#issuecomment-1376039966). Also this strictness contradicts to Markdown style of not getting in the way (ignoring errors). So this PR proposes a new strategy of dealing with errors: * In Markdown and legacy (old default) RstMarkdown we try to continue parsing, emitting only warnings * And only in pure RST mode we throw a error I expect that this strategy will be applied to more parts of markup code in the future. * Don't return anything in `checkColumns`
* fix new type inference for `noreturn` [backport] (#22182)metagn2023-06-282-7/+49
| | | | | fixes #22180 Backported since apparently the new type inference was backported
* docs nimBasePattern (#22179)Juan M Gómez2023-06-281-0/+2
|
* fixes #22001 (#22177)Andreas Rumpf2023-06-272-2/+26
| | | | | * fixes #22001 * added test case
* Revert "fix struct stat" (#22171)Andreas Rumpf2023-06-271-1/+0
| | | | | Revert "fix struct stat (#22161)" This reverts commit 4b761295e7ab31412903c02b8fb98f580bf005ca.
* fixes #22137 (#22170)Andreas Rumpf2023-06-271-1/+3
|
* Use pinned Atlas commit (#22169)Andreas Rumpf2023-06-271-1/+1
|
* adds =destroy T support for strings and seqs (#22167)ringabout2023-06-274-10/+16
| | | | | | | * adds =destroy T support for strings and seqs * fixes system * fixes tests
* destructors: update, =destroy does not require a 'var T' (#22168)Andreas Rumpf2023-06-271-3/+3
|
* fix Sigaction struct definition (#22160)Jacek Sieka2023-06-271-2/+8
| | | SigInfo is still wrong (most of its fields are in a union)
* uint arithmetic for pointers (#22159)Jacek Sieka2023-06-272-2/+2
| | | | | | | pointers are not signed and arithmetic may correctly cross int.max threshold this PR only fixes 2 occurances - there are plenty however in the std lib
* fix struct stat (#22161)Jacek Sieka2023-06-271-0/+1
| | | Undo damage of https://github.com/nim-lang/Nim/pull/14170
* fixes #22163; use `{.push warning[BareExcept]:off.}` to override settings ↵ringabout2023-06-272-6/+10
| | | | | | | temporarily (#21390) * use `{.push warning[BareExcept]:off.}` to override settings temporarily * likewise, suppress expect
* adds T destructor for refs (#22147)ringabout2023-06-263-1/+11
| | | | | | | | | * adds T destructor for refs * add `newRefdestructor` * adds ref overload for destructors * fixes config
* Fix regression in `std/times` (#22155)Jake Leahy2023-06-262-2/+6
| | | | | | | * Add simple test case Just so the regression doesn't happen again * Specify initDateTime is gcsafe in the forward declarations
* rm zero-extension and uint conversions deprecated since 0.19.9 (#22151)tersec2023-06-251-56/+0
|
* fixes #22148; std/memfiles.memSlices nesting now fails with memory sa… ↵ringabout2023-06-252-1/+16
| | | | | | | (#22154) * fixes #22148; std/memfiles.memSlices nesting now fails with memory safety capture violation * adds a test case
* make `var object` match better than `object` (#22152)metagn2023-06-252-1/+14
| | | | | | | | | | | * fix `var object` not matching better than `object` fixes #13302 * remove comment for brevity * try note * try minimize breaks
* fix VM uint conversion size bug, stricter int gen on JS (#22150)metagn2023-06-255-9/+54
| | | | | | | | | | | * fix VM uint conversion bug, stricter int gen on JS fixes #19929 * fix float -> uint64 conversion too * no need to mask to source type * simpler diff with explanation, add test for described issue
* macOS `ar` doesn't support `@` syntax (#22146)Etan Kissling2023-06-241-1/+4
| | | | | | When the linker command line is long, Nim compiler generates a file for passing the linker arguments. On `macOS`, that mechanism fails as the `@` syntax is not supported by `ar`. Use `xargs` instead to pass the linker arguments file.
* adds nimbasePattern compiler option (#22144)Juan M Gómez2023-06-244-1/+32
| | | adds optonal --nimbasepattern
* fixes #21110; duplicate proc definitions for inline iters (#21136)ringabout2023-06-222-0/+23
| | | fixes #21110; duplicate proc definitions for iters
* fixes :idx: index in in modules (2.0 regression) and in markdown files ↵ringabout2023-06-222-6/+15
| | | | | (persistent issues since 0.20.2) (#22141) fixes :idx: index
* fixes #21231; template with module as parameter elides usage/checking of ↵ringabout2023-06-212-0/+13
| | | | | | | module name specifier (#22109) * fixes #21231; template with module as parameter elides usage/checking of module name specifier * add a test case
* adds missing staticlib hints (#22140)ringabout2023-06-211-1/+1
|
* fix #20023 hash for generic tables (#20346)Bung2023-06-212-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | * fix #20023 hash for generic tables * use default computation * Update lib/pure/collections/tables.nim Co-authored-by: Dan Rose <dan@digilabs.io> * Update lib/pure/collections/tables.nim Co-authored-by: Dan Rose <dan@digilabs.io> * Update lib/pure/collections/tables.nim * Update lib/pure/collections/tables.nim * Update t20023.nim --------- Co-authored-by: Dan Rose <dan@digilabs.io> Co-authored-by: Andreas Rumpf <rumpf_a@web.de>
* Update changelog_2_0_0.md (#22135)Juan M Gómez2023-06-211-0/+4
|
* `strutils.split/rsplit` now return src on an empty sep (#22136)Zoom2023-06-215-43/+50
| | | | | | | | | | | | | | | This is a rebase of an earlier rejected PR. Following the discussion around it, this commit provides a valid output for and edge case of an empty separator for `split` and `rsplit` routines. The empty separator is interpreted as "split by no separators" and the initial string is returned. This is consistent with the behaviour of the `set[char]` version of `split`/`rsplit` routines and unifies them all. Compared to a commit merged earlier, this one has a benefit of not using assertions that will be removed in release builds and thus still not preventing possible infinite loops (which was the earlier behaviour for this edge case for separator of type `string`). Co-authored-by: Andreas Rumpf <rumpf_a@web.de>