<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>
-
URL
<The URL Structure (path only, no root url)>
-
Method:
; The stack pointer is going to be an index into the stack, and the | |
; stack is an array of words. The alternative would be to have the | |
; stack pointer me a pointer to memory, but this is perhaps a bit | |
; nicer, as where the stack actually lives is totally irrelevant. | |
@stack = global [1000 x i64] undef | |
@sp = global i64 undef; | |
; Now we have the basic stack operations: push, pop, and peek. As can | |
; be seen from the definitions, LLVM is typed, which is really nice as |
Go to File -> Settings -> Tools -> Terminal and change Shell path based on the the installed git version.
for 64bit:
"C:\Program Files\Git\bin\sh.exe" --login -i
for 32bit:
"C:\Program Files (x86)\Git\bin\sh.exe" --login -i
FROM google/dart AS dartc | |
WORKDIR /app | |
ADD pubspec.* /app/ | |
RUN pub get | |
ADD bin/ /app/bin/ | |
ADD lib/ /app/lib/ | |
RUN pub get --offline | |
RUN dart2aot /app/bin/main.dart /app/main.aot |
; The stack pointer is going to be an index into the stack, and the | |
; stack is an array of words. The alternative would be to have the | |
; stack pointer me a pointer to memory, but this is perhaps a bit | |
; nicer, as where the stack actually lives is totally irrelevant. | |
@stack = global [1000 x i64] undef | |
@sp = global i64 undef; | |
; Now we have the basic stack operations: push, pop, and peek. As can | |
; be seen from the definitions, LLVM is typed, which is really nice as |
" Location for installing plugins | |
call plug#begin('~/.vim/plugged') | |
" Other plugins are specified with user/repo on Github or x.vim on vimscripts | |
" Git integration (status bar and commands like Gblame) | |
Plug 'tpope/vim-fugitive' | |
" Add info to sidebar about git | |
Plug 'airblade/vim-gitgutter' | |
" Add file-management commands like :Delete, :Move, and :Rename | |
Plug 'tpope/vim-eunuch' |
Recommendations for getting started on Category Theory, from emilypi, in NE Scala Slack (#category-theory), 3/14/20:
Right, so let's just go through the branches and name the suggestions: