44 Matching Annotations
- Nov 2020
-
craftinginterpreters.com craftinginterpreters.com
-
“If the next token is while then do…”
parser的作用和parser為什麼需要token
-
helper
helper function is inner one
-
jlox
Lox interpreter using Java
-
4 . 7Reserved Words and Identifiers
length varied and maximal munch
-
4 . 6Longer Lexemes
length varied lexeme
-
4 . 5Recognizing Lexemes
single character lexeme
-
4 . 5 . 2Operators
lexeme up two character
-
4 . 2 . 1Token type
產生token也就是取出lexeme和決定lexeme的type是scanner的工作
-
stumble upon
碰巧遇見
Tags
Annotators
URL
-
- Sep 2020
-
theartofmachinery.com theartofmachinery.com
-
arrogant
傲慢的
-
production incidents
生產事故
-
blurted it right out
脫口說出；說漏嘴
-
turn down
拒絕
-
a little catch
小問題
-
tamer
平淡的；乏味的
-
- Feb 2020
-
docs.python.org docs.python.org
-
class dict(iterable, **kwarg)
the positional argument must be an iterable object. Each item in the iterable must itself be an iterable with exactly two objects
-
Tags
Annotators
URL
-
- Jan 2020
-
codewords.recurse.com codewords.recurse.com
-
tag of annotation type
- header
- must know
- confusing
-
It is difficult to recall a commit that is not pointed at by any ref. The further the user goes from a ref, the harder it will be for them to construct the meaning of a commit. But the further back they go, the less likely it is that someone will have changed history since they last looked5.
？？
-
Push a branch to a bare repository
????
-
Git goes to HEAD to get the parent of the a3 commit
？？
-
Merge FETCH_HEAD
-
Fetch a branch from a remote
-
Link a repository to another repository
link to a mirror repository (cloned, remote)
-
Add some files
-
Pull a branch from a remote
-
Check out a branch
-
Check out a commit
-
Clone a bare repository
delta ├── HEAD ├── config ├── objects └── refs
-
Push a branch to a checked-out branch on a remote
?????
-
Clone a repository
copy
-
Make a commit
-
you build your mental model on the truth rather than on hypotheses constructed from evidence gathered while experimenting with the API.
對git的了解不是建立在使用時的實驗和猜測
-
Initialize the repository
-
The first entry is for data/letter.txt. The content of this file is a in the base, b in the receiver and a in the giver. The content is different in the base and receiver. But it is the same in the base and giver. Git sees that the content was modified by the receiver, but not the giver. The diff entry for data/letter.txt is a modification, not a conflict.
the content flow before merging in two branches
- base: 'a' -> receiver: 'a' (receiver is unmodified after base)
- base: 'a' -> giver: 'b' (receiver is modified after base) ##### the content flow after merging
- receiver: 'a' -> giver: 'b' (giver is modified after receiver and don't have any conflict)
-
It gets the giver commit
deputy
-
superseded
代替
-
working copy
「作業用副本」亦即，正本歸檔，副本作業
-
100664
represent "file permission"
-
It creates a tree graph to represent the content of the version of the project being committed
不同提交版本建立的樹、圖型結構
-
This command creates a new blob with the new content. And it updates the index entry for data/number.txt to point at the new blob.
-
They make the correction and add the file to the index again
-
-
localhost:8080 localhost:8080
-
it's due for release
k
-
due for
預計應到的（時間）
-