José Paulo

I don't have a suggestion. What could be done, at least for those who use it and want to investigate why a previous version broke, is to create a file...

From the research I did, adding `class="hljs"`, in the `` tags, of the inline code, would solve the problem. However, in a quick look at the `nimibook` code, I saw...

Today, after recompiling from HEAD, I checked the files that were used to compile nimlangserver and it didn't even use anything from stdlib or the Nim compiler that was installed...

> This sounds more like a nim/nimble bug than one in langserver? ie the purpose of a lock file is to deterministically choose which libraries are used to compile the...

Was removed in 8449dfbf6d6f40236230f4f79856cb8708a5b98c

The error you reported in "nim-lang.Nim (Windows_amd64_batch1_3 packages)" has to do with this problem here: #19537 As for the problem in "nim-lang.Nim (OSX_amd64_cpp packages)" I have no idea, but I...

> IMO easiest way to support XP is to use [`RtlGenRandom`](https://docs.microsoft.com/en-us/windows/win32/api/ntsecapi/nf-ntsecapi-rtlgenrandom) in first place (that is `SystemFunction036` export of `advapi32.dll`). > > It does not need a handle being opened/closed...

@xflywind I wanted to hear from you who added sysrand if there was any discussion about the Windows API and any objections to RtlGenRandom...

Thank you for the report. The current behavior is intentional, as overflow detection is not implemented. It's something I've been studying how to implement in the best possible way. The...

The problem with the JS backend is that it does not support 64-bit integers and the Int128 and UInt128 object use 64-bit integers. At the time I designed nint128 I...