dash-3d-tmp
/
phd
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Merge branch 'master' of gitea.tforgione.fr:tforgione-phd/phd

This commit is contained in:
Thomas Forgione 2019-10-29 18:23:10 +01:00
parent 3cbc9e5106 8767ee4c5f
commit d8a2f0332a
No known key found for this signature in database
GPG Key ID: BFD17A2D71B3B5E7
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
src/bib.bib
View File

@ -468,30 +468,30 @@
} }
@misc{so-survey-2016, @misc{so-survey-2016,
title = {Developer Survey Results 2016}, title = {Stack Overflow Developer Survey Results},
year = {2016}, year = {2016},
author = {Stack Overflow}, author = {},
howpublished = {\url{https://insights.stackoverflow.com/survey/2016#technology-most-loved-dreaded-and-wanted}} howpublished = {\url{https://insights.stackoverflow.com/survey/2016#technology-most-loved-dreaded-and-wanted}}
} }
@misc{so-survey-2017, @misc{so-survey-2017,
title = {Developer Survey Results 2017}, title = {Stack Overflow Developer Survey Results},
year = {2017}, year = {2017},
author = {Stack Overflow}, author = {},
howpublished = {\url{https://insights.stackoverflow.com/survey/2017#technology-most-loved-dreaded-and-wanted}} howpublished = {\url{https://insights.stackoverflow.com/survey/2017#technology-most-loved-dreaded-and-wanted}}
} }
@misc{so-survey-2018, @misc{so-survey-2018,
title = {Developer Survey Results 2018}, title = {Stack Overflow Developer Survey Results},
year = {2018}, year = {2018},
author = {Stack Overflow}, author = {},
howpublished = {\url{https://insights.stackoverflow.com/survey/2018#technology-most-loved-dreaded-and-wanted}} howpublished = {\url{https://insights.stackoverflow.com/survey/2018#technology-most-loved-dreaded-and-wanted}}
} }
@misc{so-survey-2019, @misc{so-survey-2019,
title = {Developer Survey Results 2019}, title = {Stack Overflow Developer Survey Results},
year = {2019}, year = {2019},
author = {Stack Overflow}, author = {},
howpublished = {\url{https://insights.stackoverflow.com/survey/2019#technology-most-loved-dreaded-and-wanted}} howpublished = {\url{https://insights.stackoverflow.com/survey/2019#technology-most-loved-dreaded-and-wanted}}
} }

2
src/foreword/implementation.tex
View File

@ -113,7 +113,7 @@ And effectively, the borrow checker will crash the compiler with the error in Li
\end{figure} \end{figure}
This example is one of the many examples of how powerful the borrow checker is: in Rust code, there can be no dangling reference, and all the segmentation faults coming from them are detected by the compiler. This example is one of the many examples of how powerful the borrow checker is: in Rust code, there can be no dangling reference, and all the segmentation faults coming from them are detected by the compiler.
The borrow checker may seem like an enemy to newcomers because it often rejects code that seem correct, but once one get used to it, they understand what is the problem with their code and either fix the problem easily, or realise that the whole architecture is wrong and understand why. The borrow checker may seem like an enemy to newcomers because it often rejects code that seem correct, but once one gets used to it, they understand what is the problem with their code and either fix the problem easily, or realise that the whole architecture is wrong and understand why.
It is probably for those reasons that Rust is the \emph{most loved programming language} according to the Stack Overflow Developer Survey in~\citeyear{so-survey-2016,so-survey-2017,so-survey-2018} and~\citeyear{so-survey-2019}. It is probably for those reasons that Rust is the \emph{most loved programming language} according to the Stack Overflow Developer Survey in~\citeyear{so-survey-2016,so-survey-2017,so-survey-2018} and~\citeyear{so-survey-2019}.