Skip to content

Commit 66b27ef

Browse files
awmorganaykevl
authored andcommitted
fix typo
packkage->package
1 parent a2b56f5 commit 66b27ef

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/docs/guides/contributing/organization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The `GOROOT` directory in TinyGo is actually a constructed GOROOT, cached and re
2626

2727
These replaced (or added) packages live in the src subdirectory:
2828

29-
- `src/runtime`: the replacement runtime package that contains the things you would expect of a runtime package. It implements a heap with a garbage collector, a scheduler for goroutines, channels, and perhaps less obviously: it contains various things that are not implemented in the compiler like maps, the slice `append` built-in, and various other language features. It also implements a few device specific things, namely: runtime initialization and timers (used by the time packkage). These last two are device specific and need to be implemented per device.
29+
- `src/runtime`: the replacement runtime package that contains the things you would expect of a runtime package. It implements a heap with a garbage collector, a scheduler for goroutines, channels, and perhaps less obviously: it contains various things that are not implemented in the compiler like maps, the slice `append` built-in, and various other language features. It also implements a few device specific things, namely: runtime initialization and timers (used by the time package). These last two are device specific and need to be implemented per device.
3030
- `src/device`: contains hardware register access (memory-mapped I/O) without abstractions. Most of the subpackages are automatically generated. These packages are only used for baremetal programming.
3131
- `src/machine`: contains a hardware abstraction layer for chips. You could think of this as the equivalent of the `os` package: it provides portable APIs for common hardware peripherals. For example, every chip vendor implements [I2C]({{<ref "i2c.md">}}) differently but the machine package wraps this in a single `*machine.I2C` type that has the same interface on any supported chip. For more information, see the [machine package doucumentation]({{<ref "../../reference/machine.md">}})
3232

0 commit comments

Comments
 (0)