Skip to content

Commit

Permalink
Doc Typo Fixes
Browse files Browse the repository at this point in the history
Fixup some mis-spellings and other minor doc issues.
  • Loading branch information
iwillspeak committed Feb 10, 2019
1 parent 1faba9f commit 62353ee
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 13 deletions.
2 changes: 1 addition & 1 deletion LICENSE.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,4 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,10 @@ Ullage is open source, under the [MIT License](LICENSE.md).

### Lexer

* [x] Recognise words, numbers, comments, operators and whitespace
* [x] Recognise words, numbers, comments, operators and white-space
* [x] Position information on each token
* [ ] Interpolated strings
* [ ] Expose whitespace to the parser
* [x] Expose whitespace to the parser

### Parser

Expand Down
2 changes: 1 addition & 1 deletion STRUCTURE.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The language parser and compiler are written in Rust. The source lives in the `s

Functional tests for the language consist of a set of source files in `spec/`. These files contain specially formatted comments which are interpreted by the Python test runner `specs.py` when run.

Documentation, written in Markdown, is in the `docs/` folder. It can be compiled into a static side with [`docket`](http://willspeak.me/docket/).
Documentation, written in Markdown, is in the `docs/` folder. It can be compiled into a static site with [`docket`](http://willspeak.me/docket/).

## Rust modules

Expand Down
8 changes: 0 additions & 8 deletions docs/10-syntax.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,14 +170,6 @@ print add(add(1, 2), 3) # => 6
The following grammar defines the language:


```
def foo(bar):
pass
```


:::python

identifier = WORD
;

Expand Down
2 changes: 1 addition & 1 deletion docs/15-data-layout.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,4 +38,4 @@ Rather than aiming to control access to data as Rust does the language should pr
* Reference counting. E.g. Swift's ARC & Python.
* Simple mark & sweep GC.

For a full mark and sweep or other collector the code generated needs to insert GC statepoints. For this reason i'm tempted to head towards the second option. I place of statepoints we will need to decide in the lower pass where to insert RC retain and release code to maintain the count. Could this work the same way as Rust's ARC model? In that case the code just needs to know a fixed point in the scope where each value is deallocated.
For a full mark and sweep or other collector the code generated needs to insert GC statepoints. For this reason i'm tempted to head towards the second option. I place of statepoints we will need to decide in the lower pass where to insert RC retain and release code to maintain the count. Could this work the same way as Rust's ARC model? In that case the code just needs to know a fixed point in the scope where each value is deallocated.

0 comments on commit 62353ee

Please sign in to comment.