jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

manual_experiments: clarifications

Browse source
This commit is contained in:
Araq 2019-05-15 17:39:37 +02:00
commit a470ba673b
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/manual_experimental.rst
View file

@ -17,13 +17,16 @@ Some of these are not covered by the ``.experimental`` pragma or
one may want to use Nim libraries using these features without using them one may want to use Nim libraries using these features without using them
oneself. oneself.
**Note**: Unless otherwise indicated, these features are not to be removed,
but refined and overhauled.
Package level objects Package level objects
===================== =====================
Every Nim module resides in a (nimble) package. An object type can be attached Every Nim module resides in a (nimble) package. An object type can be attached
to the package it resides in. If that is done, the type can be referenced from to the package it resides in. If that is done, the type can be referenced from
other modules as an `incomplete`:idx: object type. This features allows to other modules as an `incomplete`:idx: object type. This feature allows to
break up recursive type dependencies accross module boundaries. Incomplete break up recursive type dependencies accross module boundaries. Incomplete
object types are always passed ``byref`` and can only be used in pointer like object types are always passed ``byref`` and can only be used in pointer like
contexts (``var/ref/ptr IncompleteObject``) in general since the compiler does contexts (``var/ref/ptr IncompleteObject``) in general since the compiler does