diff options
Diffstat (limited to 'doc/intern.md')
| -rw-r--r-- | doc/intern.md | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/intern.md b/doc/intern.md index fe2e59f51..6b16bc71f 100644 --- a/doc/intern.md +++ b/doc/intern.md @@ -107,6 +107,10 @@ You can also bisect using custom options to build the compiler, for example if you don't need a debug version of the compiler (which runs slower), you can replace `./koch temp`:cmd: by explicit compilation command, see [Bootstrapping the compiler]. +See also: + +- Crossplatform C/Cpp/Valgrind/JS Bisect in GitHub: https://github.com/juancarlospaco/nimrun-action#examples + Building an instrumented compiler --------------------------------- @@ -364,7 +368,7 @@ Files that may need changed for your platform include: Add os/cpu to `Project.Platforms` field. * `lib/system/platforms.nim` Add os/cpu. -* `lib/pure/include/osseps.nim` +* `std/private/osseps.nim` Add os specializations. * `lib/pure/distros.nim` Add os, package handler. @@ -593,14 +597,14 @@ Integer literals In Nim, there is a redundant way to specify the type of an integer literal. First, it should be unsurprising that every node has a node kind. The node of an integer literal can be any of the -following values:: +following values: nkIntLit, nkInt8Lit, nkInt16Lit, nkInt32Lit, nkInt64Lit, nkUIntLit, nkUInt8Lit, nkUInt16Lit, nkUInt32Lit, nkUInt64Lit On top of that, there is also the `typ` field for the type. The kind of the `typ` field can be one of the following ones, and it -should be matching the literal kind:: +should be matching the literal kind: tyInt, tyInt8, tyInt16, tyInt32, tyInt64, tyUInt, tyUInt8, tyUInt16, tyUInt32, tyUInt64 @@ -656,7 +660,6 @@ pointing back to the integer literal node in the ast containing the integer value. These are the properties that hold true for integer literal types. -:: n.kind == nkIntLit n.typ.kind == tyInt n.typ.n == n |