* ko: refresh translation for concurrency
Part of #925.
* ko: move translation back to where it belongs
This is likely outdated, but moving it here helps avoid conflicts. The
outdated paragraph can be cleaned up with `msgmerge` at a later point.
* ko: refresh translation for android
Part of #925.
* ko: move translations back to where they belong
Moving them back helps avoid conflicts. The outdated paragraphs can be
cleaned up with `msgmerge` at a later point.
* ko: refresh translation for pattern-matching
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: move translation back to where it belongs
This is likely outdated, but moving it here helps avoid conflicts. The
outdated paragraph can be cleaned up with `msgmerge` at a later point.
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for generics
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: move translation back to where it belongs
This paragraph is likely outdated, but moving it here helps avoid
conflicts. The outdated paragraph can be cleaned up with `msgmerge` at
a later point.
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Added steps to configure Poedit properly
* Small adjustments
* Add link to Poedit
* Fix file formatting
* One. More. dprint. Fix.
* Normalizes pt-BR.po file format through Poedit
with line wrap.
* Fix typo.
* Fix fuzzy entries after .po file reformatting.
* Fix one code sample
* Added steps to configure Poedit properly
* Small adjustments
* Add link to Poedit
* Fix file formatting
* One. More. dprint. Fix.
* Normalizes pt-BR.po file format through Poedit
with line wrap.
* Fix typo.
* ko: refresh translation for modules
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Update po/ko.po
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for testing
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for basic-syntax
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Update po/ko.po
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for welcome
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for control-flow
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for SUMMARY
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for credits
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for running-the-course
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Rebase and move translations to correct spot
I believe the PO file would benefit from a msgmerge run. I’ll let the
translators do this after merging all outstanding translations.
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* ko: refresh translation for enums
Part of #925.
* Apply suggestions from code review
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
---------
Co-authored-by: Jiyong Park <55639800+jiyongp@users.noreply.github.com>
* Fix solution in Link Checker in Concurrency Morning exercises.
This change fixes the following issues with the current solution:
1. It is not listed on the "solutions" page.
2. It is not multi-threaded and does not use channels.
---------
Co-authored-by: Dustin J. Mitchell <djmitche@google.com>
* compound types: disambiguate that length is not 'same'
* basic syntax: clarify preference for consts and quickly justify unsafety of static mut
* basic-syntax: take review feedback into account on consts/statics
* basic-syntax: be careful not to call `const` defns variables
variables in rust are `place`s in a formal sense and name objects in an informal one; `const` merely abbreviates an expression
* removed $ from code-blocks in build_all.sh
* separate the code from the output
* added shell indicator for the code block
* added shell indicator for the code block
* update logging.md
* separate the code from the output in other files as well
* update the output code-blocks to text
* exercises: health-statistics: weight -> height
weight may be a sensitive topic for some readers; use height instead as this isn't important to the content of the course
* exercises: health-statistics: add health report
this lets us see a non-setter use case for &mut self
it also makes the 'statistics' side of this exercise more explicit as we count doctor visits
* exercises: health-statistics: normalize variable names
* remove $ from code blocks in translations
* remove $ from code blocks in the other markdown files as well
* Revert "remove $ from code blocks in the other markdown files as well"
This reverts commit eda922dab9.
* remove $ from code blocks in setup.md
* re-added the previous changes
* revert logging.md
Outlines an alternative implementation for Polygon::length. This exercise is aimed at novice users and we want to keep the implementation simple. For users familiar with iterator concepts this comment points to an alternative.
