Course Structure
๊ฐ์๋ ๋น ๋ฅธ ์๋๋ก ์งํ๋๋ฉด ๋ค์ 3,4์ผ๋์ ๋ง์ ๋ฒ์์ ๋ถ๋ถ์ ๋ค๋ฃน๋๋ค.
The course is fast paced and we will cover a lot of ground over the next 3โ4 days:
- 1์ผ์ฐจ: ๋ฌ์คํธ ๊ธฐ๋ณธ, ์์ ๊ถ(ownership)๊ณผ ๋น๋ฆผ(borrow) ์ฒดํฌ.
- 2์ผ์ฐจ: ๋ณตํฉ ๋ฐ์ดํฐ ์ ํ, ํจํด ๋งค์นญ, ํ์ค ๋ผ์ด๋ธ๋ฌ๋ฆฌ
- 3์ผ์ฐจ: ํธ๋ ์(traits)๊ณผ ์ ๋๋ฆญ(generics), ์๋ฌ ํธ๋ค๋ง(์ค๋ฅ ์ฒ๋ฆฌ), ํ ์คํธ, ์์ ํ์ง ์์ ๋ฌ์คํธ.
- 4์ผ์ฐจ: ๋ฌ์คํธ์ ๋์์ฑ ๋ฐ ๋ค๋ฅธ ์ธ์ด์์ ์ํธ ์ด์ฉ์ฑ
- Day 1: Basic Rust, ownership and the borrow checker.
- Day 2: Compound data types, pattern matching, the standard library.
- Day 3: Traits and generics, error handling, testing, unsafe Rust.
- Day 4: Concurrency in Rust and interoperability with other languages
4์ผ์ฐจ์ ์ฐ์ต: ๋ฌ์คํธ ํ๋ก์ ํธ์์ C/C++๋ก ์์ฑ๋ ์ฝ๋๋ฅผ ์ด์ ํด์ ์ฐ๊ฒฐํ๋ ค๊ณ ํ๋ค๋ฉด ์ข ์์ฑ์ด ์ ์ ์๋ก ์ข์ต๋๋ค. ์ฝ๋๋ฅผ ๊ตฌ๋ฌธ๋ถ์ํ๋ ๊ฒ์ด ์ด์์ ์ ๋๋ค.
Exercise for Day 4: Do you interface with some C/C++ code in your project ๋ฉด which we could attempt to move to Rust? The fewer dependencies the better. Parsing code would be ideal.
Format
๊ฐ์๋ ๋ํ์์ด๋ฉฐ ๋น์ ์ ์ง๋ฌธ์ด ๋ฌ์คํธ ํํ์ ์ด๋ ๊ฒ์ ๋๋ค!
The course is interactive and your questions will drive our exploration of Rust!
- ์ง๋ฌธ์ด ์๊ธฐ๋ฉด ์ง๋ฌธํด์ฃผ์ธ์
- ํ ๋ก ์ ๋งค์ฐ ๊ถ์ฅ๋ฉ๋๋ค!
- ๊ฐ์์ ์๋ฃ๋ ์ฐธ๊ณ ์๋ฃ์ผ ๋ฟ์ผ๋ก ๊ฑด๋๋ ์ ์์ต๋๋ค.
- Please ask questions when you get them, donโt save them to the end.
- Discussions are very much encouraged!
- We will likely talk about things ahead of the slides.
- The slides are just a support and we are free to skip them as we like.