-
-
The issue #10241 still occurs, but with slightly different code.
### Example
Modified test case for #10322 has the same issue as reported:
```nim
type
String* {.importcpp: "std::string", head…
-
It's an open secret that I've some criticisms of async/await:
## Fear of Threads
From the perspective of a newcomer who is looking to transfer existing
knowledge or code from another language t…
-
`const char*` is returned by some C/C++ functions, but it (usually) can't be represented in Nim. Sometimes we use `cstring` for it, which may cause problems because many C++ compilers insist that they…
-
Recently, the official compiler has been open-sourced as part of the [neverwinter.nim](https://github.com/niv/neverwinter.nim) project. This compiler matches the toolset capabilities, and updates to t…
-
When a generic type has multiple generic parameters, it's not possible to instantiate types that share the same concrete type for the first generic parameter.
### Example
```nim
import hashes, …
-
### Example
```nim
{.experimental: "notnil".}
template newClone*[T](x: T): ref T not nil =
let res = new typeof(x)
res[] = x
res
let x = newClone(0)
quit x[]
```
### Current Ou…
-
Sorry, I can't think of any meaningful summary for this bug
### Example
```nim
import macros
proc take(x: proc(): bool) = discard
macro triggerBug(updId: bool): untyped =
assert updId.bo…
-
Output that doesn't come from the compiler always appears. I'm currently using Windows 10.
ghost updated
8 years ago
-
Example/testing repository, where this can be demonstrated and where solution can be tested: https://github.com/OK-DMR/dmr-kaitai
Currently I have [bash script rebuild-all.sh](https://github.com/OK…