View Code? Open in Web Editor
NEW
A selection of textbook-like course notes for the Imperial College Computing modules.
Home Page: https://oliverkillane.github.io/Imperial-Computing-Notes/
License: MIT License
TeX 82.75%
Python 1.44%
Shell 0.36%
C++ 8.10%
Kotlin 0.06%
Haskell 3.29%
Rust 0.91%
Elixir 0.91%
C 0.23%
TLA 0.52%
Assembly 0.16%
CMake 0.42%
Dockerfile 0.11%
Java 0.69%
HTML 0.04%
imperial-computing-notes's Introduction
imperial-computing-notes's People
Contributors
Watchers
imperial-computing-notes's Issues
Needs a cleanup - I skipped over the content quickly due to familiarity.
Specifically adding:
- Non-Assessed Channels in Rust
- Send & Sync traits
- Examples for interior mutability pattern
Needs an overhaul to include tutorial material.
Specifically PSO, and walkthroughs for SC, TSO, RA, COH as shown in
Specifically:
- Sorting algorithm implementations
- Database normalisation
- Partitioning
- B* Trees
Majority of the content is still unfinished
Page 6 data processing
๐
- Add a basic script to tools to install the lexer (hwayne TLA lexer) within pygments
- Switch TLA source code inputs to use lexer
- Check possibility of highlighting
.cfg
files also
Description
The proof tree notation is done using \cfrac
s in a maths environment, this is not ideal as:
- side tags are part of the width of the
\cfrac
- no proper centering control
I recently did a CW with bussproofs and like this style.
In the long term, should probably move to using this.
Missing chapters to be completed:
Could also include:
Also need to get a final review from a few fresh eyes (hopefully some volunteers this term)
RW Lock differs from lectures.
- Waiting confirmation from lecturer on correctness of lecture content here
- Need to fix and improve current Lock Manager implementation in
transactions/code
Definitionbox for futex is empty
Description
Currently the content is included in their directories (copy pasted from old 2nd year repo
Goals
- Make it easier to develop notes
- Need to make an image / devcontainer setup to make it possible to work on these notes:
- Linting check as part of the CI, or a lint as a precommit hook
Maybe Goals?
- Separating built pdfs from repo, and building in the CI [Problem: How to review pdfs from pull requests?]
- Better helper scripts [Move to python, nicer messages, simple commands for build, maybe? -
icn build
, icn check
etc]
Required Changes
- Docker image built in repo and published to ghcr
- added as
.devcontainer
with vscode settings & extensions setup
Needs to include:
- Latex distribution + packages + latexindent
- Language support for C++, elixir, haskell, rust, TLA, python
- Pygments (+ add TLA highlighting for distributed notes)
- Inkscape
Required Test
- To be able to edit code, latex & diagrams from github codespaces by just opening the repo in codespaces / no setup required.
With history G, I think you meant for B q:7
and B q.deq()
to be swapped around.
Nice notes man, I'm finding them really helpful compared to the slides.