| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
| |
Respect `--gcc.exe` and similar options when `--genScript:on` is used.
|
| |
|
| |
extend the skipAddr for potential types
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Add example object into testproject
The proc is there to check the case of an identDef being inside an identDef (We do want to render those even if they are not exported)
* Add `inside` set to `TSrcGen` which allows us to see what context we are in
This is done instead of adding another inXyz bool parameter
We then use this to know if we are inside an object when rendering an nkIdentDefs (To know if we need to skip rendering it)
* Update test files
|
| |
|
|
|
| |
* Fixes Naive virtual crash the compiler fixes #22269
* adds type specific test
|
| | |
|
| |
|
| |
* Fix #22273
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
loop in ORC (#22240)
fixes #22237; fixes #21160; wrong cursor on unowned parameters
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add tests
Also test if exported all tuple fields works. This seems like a hacky solution so will try and dive further to find a better solution
* Always suggest tuple fields if it passes the filter
If the tuple we are accessing is in scope then all the fields will also be in scope
* Update tests so line numbers are correct
|
| | |
|
| |
|
|
|
| |
* .
* Fix #21595
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
(#22213)
fixes #22212; Compile error when running a Nimscript that compares seq with switch("mm", "arc")
|
| |
|
|
|
| |
(#22211)
fixes #22208; Ambiguous error when import modules with same names but different aliases
|
| | |
|
| | |
|
| |
|
|
|
| |
* fixes #22200
* typo
|
| |
|
|
|
| |
* 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
|
| | |
|
| | |
|
| |
|
| |
the function actually returns
|
| |
|
|
|
|
|
| |
* changelog improvements
* changelog that people want to actually read
* improvements
|
| |
|
| |
fixes #22187
|
| |
|
|
| |
(#22184)
|
| |
|
|
|
|
|
| |
* 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
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`
|
| |
|
|
|
| |
fixes #22180
Backported since apparently the new type inference was backported
|
| | |
|
| |
|
|
|
| |
* fixes #22001
* added test case
|
| |
|
|
|
| |
Revert "fix struct stat (#22161)"
This reverts commit 4b761295e7ab31412903c02b8fb98f580bf005ca.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* adds =destroy T support for strings and seqs
* fixes system
* fixes tests
|
| | |
|
| |
|
| |
SigInfo is still wrong (most of its fields are in a union)
|
| |
|
|
|
|
|
| |
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
|
| |
|
| |
Undo damage of https://github.com/nim-lang/Nim/pull/14170
|
| |
|
|
|
|
|
| |
temporarily (#21390)
* use `{.push warning[BareExcept]:off.}` to override settings temporarily
* likewise, suppress expect
|
| |
|
|
|
|
|
|
|
| |
* adds T destructor for refs
* add `newRefdestructor`
* adds ref overload for destructors
* fixes config
|