rename 'designing a library' example
library design in Rust is its own topic that this course does not cover; to avoid confusion, let's stick to describing things in terms of books
In C (as opposed to C++) the explicit cast from void* to int* is not required. It is also not idiomatic to do so in C code.
Actual C codebase would use `malloc()` without the cast, and a C++ one (when not using abstractions) a `new int[n]` - both a bit cleaner and less verbose than this example.
Clarify that each philosopher should think/eat 100 times.
Folks who have hazy memories of the philosopher dining problem may
interpret the original instructions as "make each philosopher think and
eat once". This interpretation loses a critical detail, because the
resulting code is highly unlikely to deadlock in practice, even without
breaking the symmetry.
* Add missing binaries in TRANSLATIONS.md instructions.
With these instructions, I can start from a clean fork, and get running
quickly.
* Update TRANSLATIONS.md: Add Debian
Co-authored-by: Martin Geisler <martin@geisler.net>
* Update TRANSLATIONS.md, format.
* Remove duplicate info between README and TRANSLATIONS.
---------
Co-authored-by: Martin Geisler <martin@geisler.net>
* Suggest to run day 3 afternoon exercise locally
Based on feedback from running the class, students found developing
the day 3 afternoon exercise locally was a better experience than
using Playground.
* Update src/exercises/day-3/afternoon.md
---------
Co-authored-by: Martin Geisler <martin@geisler.net>
* Completing and improving pt-BR translation for
chapter 1.
* Small typo fix.
* Some other fixes.
* pt-BR: Updates/completes translations for ch 1-6
* Fix missing '\n'
* zh-TW: translate cargo
Part of #684.
* Apply suggestions from code review
Co-authored-by: Jonathan Hao <phao@chromium.org>
* Use 建構 for build instead of 建立
---------
Co-authored-by: Jonathan Hao <phao@chromium.org>
Co-authored-by: Jonathan Hao <phao@google.com>
* zh-TW: translate ownership
Part of #684.
* Apply suggestions from code review
Co-authored-by: Jonathan Hao <phao@chromium.org>
* Replace "擁有權" with "所有權"
* Remove "__"
---------
Co-authored-by: Jonathan Hao <phao@chromium.org>
Co-authored-by: Jonathan Hao <phao@google.com>
* zh-CN: translate src/basic-syntax/variables.md, src/basic-syntax/type-inference.md and some words in SUMMARY.md (#796)
* zh-CN: translate src/basic-syntax/variables.md, src/basic-syntax/type-inference.md and some words in SUMMARY.md
* Use "类型推导" for "Type Inference"
* Update translation in src/basic-syntax/type-inference.md
Co-authored-by: whd <7058128+superwhd@users.noreply.github.com>
* Update translation in src/basic-syntax/variables.md
Co-authored-by: whd <7058128+superwhd@users.noreply.github.com>
* Update translation in src/basic-syntax/type-inference.md
* Add newlines inside translation at src/basic-syntax/type-inference.md:28
* Revert "Update translation in src/basic-syntax/type-inference.md"
This reverts commit 5119474c1c.
* zh-CN: use `#, fuzzy` instead of FIXME comment in basic-syntax/type-inference.md
---------
Co-authored-by: Zhang Rui <me@zhrichard.me>
Co-authored-by: whd <7058128+superwhd@users.noreply.github.com>
* ja: Ch5.0 #652
・not confident about the translation "access to low-level hardware"
* ja: Ch.5.1 #652
* ja: Ch.5.2 #652
・"integer overflow is defined" -> 「整数オーバーフローの挙動が定義されている」 not confident here
* ja: Ch.5.3 #652
・a tad nit-picky, but believe the "The reasoning behind this..." should be on a line of its own, adding a "\n" between any of the three bullet points can fix this, BUT it will add a line between them. I personally prefer adding the "\n", but left as is
* ja: Ch.5 #652
fixes suggested by @keiichiw
Just like the Markdown files in #846, we cannot generate a redirect
for the LICENSE file this way. The broken link was fixed in #813, so
we should be fine here.
* Run builds on both Mac OS and Linux
This would have helped us catch #570.
* Fix MacOS CI (#848)
* Revert unnecessary changes
The changes might be good, but I want to keep this PR small and
focused. If we end up with the extra `cfg` statements, we should
include a comment to let students know what they do: we’re targeting
people new to Rust, so we need to be careful with explanations.
---------
Co-authored-by: Dominik Maier <domenukk@gmail.com>
