context at instantiation are considered: In the example, the generic `==` for tuples (system.html#%3D%3D%2CT%2CT_2) (as de�ned in the system module) uses the == operators of the tuple's components. However lib/pure/strutils.toUpperAscii("abc") import lib/pure/strutils as strutils import "gfx/3d/somemodule" # in quotes because '3d' is not a valid Nim identifier From import statement After the from keyword, a

echo lib/pure/strutils.toUpperAscii("abc") import lib/pure/strutils as strutils import "gfx/3d/somemodule" # '3d' 不是合法的 Nim 标识符，要⽤引号 如果要导⼊模块 module ，⼜要强制以全限定的形式访问它的每⼀个符号，那么可以 from module import nil 。

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D positions. When we insert, move or delete a position value, it may occur that we get duplicates, with reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. Using a game engine, or only a simple library like cairo, sdl2

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D positions. When we insert, move or delete a position value, it may occur that we get duplicates, with reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. Using a game engine, or only a simple library like cairo, sdl2

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D positions. When we insert, move or delete a position value, it may occur that we get duplicates, with reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. 374 Using a game engine, or only a simple library like cairo

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D posi­ tions. When we insert, move or delete a position value, it may occur that we get duplicates reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. Using a game engine, or only a simple library like cairo, sdl2

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D positions. When we insert, move or delete a position value, it may occur that we get duplicates, with reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. 374 Using a game engine, or only a simple library like cairo

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D posi­ tions. When we insert, move or delete a position value, it may occur that we get duplicates reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. Using a game engine, or only a simple library like cairo, sdl2

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D posi­ tions. When we insert, move or delete a position value, it may occur that we get duplicates reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. Using a game engine, or only a simple library like cairo, sdl2

remove the adjacent duplicates. A typical use case for that is when we have stored a path of 2D or 3D posi­ tions. When we insert, move or delete a position value, it may occur that we get duplicates reason is, that for a section about games, we would have to make a lot of decisions in advance: 2D or 3D game, action game, or strategy game. Using a game engine, or only a simple library like cairo, sdl2