Archives/patterns
2
1
Fork 0
mirror of https://github.com/rust-unofficial/patterns synced 2024-11-10 13:10:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 78735669af

Browse Source
This commit is contained in:
simonsan 2022-03-17 13:02:39 +00:00
parent f5ff4bb3c6
commit b2dafa0006
5 changed files with 50 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
index.html
View File

@ -150,26 +150,27 @@ are generically applicable.</p>
<p>Design patterns are a collection of reusable and tested solutions to <p>Design patterns are a collection of reusable and tested solutions to
recurring problems in engineering. They make our software more modular, recurring problems in engineering. They make our software more modular,
maintainable, and extensible. Moreover, these patterns provide a common maintainable, and extensible. Moreover, these patterns provide a common
language for developers to use, making them an excellent tool for effective language for developers, making them an excellent tool for effective
communication when problem-solving in teams.</p> communication when problem-solving in teams.</p>
<h2 id="design-patterns-in-rust"><a class="header" href="#design-patterns-in-rust">Design patterns in Rust</a></h2> <h2 id="design-patterns-in-rust"><a class="header" href="#design-patterns-in-rust">Design patterns in Rust</a></h2>
<p>There are many problems that share the same form. <p>Rust is not object-oriented, and the combination of all its characteristics,
Due to the fact that Rust is not object-oriented, design patterns vary with such as functional elements, a strong type system, and the borrow checker,
respect to other object-oriented programming languages. makes it unique.
While the details are different, since they have the same form they can be Because of this, Rust design patterns vary with respect to other
solved using the same fundamental methods:</p> traditional object-oriented programming languages.
That's why we decided to write this book. We hope you enjoy reading it!
The book is divided in three main chapters:</p>
<ul> <ul>
<li><a href="./patterns/index.html">Design patterns</a> are methods to solve common problems <li><a href="./idioms/index.html">Idioms</a>: guidelines to follow when coding.
when writing software.</li> They are the social norms of the community.
<li><a href="./anti_patterns/index.html">Anti-patterns</a> are methods to solve these same You should break them only if you have a good reason for it.</li>
common problems. However, while design patterns give us benefits, <li><a href="./patterns/index.html">Design patterns</a>: methods to solve common problems
when coding.</li>
<li><a href="./anti_patterns/index.html">Anti-patterns</a>: methods to solve common problems
when coding.
However, while design patterns give us benefits,
anti-patterns create more problems.</li> anti-patterns create more problems.</li>
<li><a href="./idioms/index.html">Idioms</a> are guidelines to follow when coding.
They are social norms of the community.
You can break them, but if you do you should have a good reason for it.</li>
</ul> </ul>
<p>TODO: Mention why Rust is a bit special - functional elements, type system,
borrow checker</p>
</main> </main>

31
intro.html
View File

@ -150,26 +150,27 @@ are generically applicable.</p>
<p>Design patterns are a collection of reusable and tested solutions to <p>Design patterns are a collection of reusable and tested solutions to
recurring problems in engineering. They make our software more modular, recurring problems in engineering. They make our software more modular,
maintainable, and extensible. Moreover, these patterns provide a common maintainable, and extensible. Moreover, these patterns provide a common
language for developers to use, making them an excellent tool for effective language for developers, making them an excellent tool for effective
communication when problem-solving in teams.</p> communication when problem-solving in teams.</p>
<h2 id="design-patterns-in-rust"><a class="header" href="#design-patterns-in-rust">Design patterns in Rust</a></h2> <h2 id="design-patterns-in-rust"><a class="header" href="#design-patterns-in-rust">Design patterns in Rust</a></h2>
<p>There are many problems that share the same form. <p>Rust is not object-oriented, and the combination of all its characteristics,
Due to the fact that Rust is not object-oriented, design patterns vary with such as functional elements, a strong type system, and the borrow checker,
respect to other object-oriented programming languages. makes it unique.
While the details are different, since they have the same form they can be Because of this, Rust design patterns vary with respect to other
solved using the same fundamental methods:</p> traditional object-oriented programming languages.
That's why we decided to write this book. We hope you enjoy reading it!
The book is divided in three main chapters:</p>
<ul> <ul>
<li><a href="./patterns/index.html">Design patterns</a> are methods to solve common problems <li><a href="./idioms/index.html">Idioms</a>: guidelines to follow when coding.
when writing software.</li> They are the social norms of the community.
<li><a href="./anti_patterns/index.html">Anti-patterns</a> are methods to solve these same You should break them only if you have a good reason for it.</li>
common problems. However, while design patterns give us benefits, <li><a href="./patterns/index.html">Design patterns</a>: methods to solve common problems
when coding.</li>
<li><a href="./anti_patterns/index.html">Anti-patterns</a>: methods to solve common problems
when coding.
However, while design patterns give us benefits,
anti-patterns create more problems.</li> anti-patterns create more problems.</li>
<li><a href="./idioms/index.html">Idioms</a> are guidelines to follow when coding.
They are social norms of the community.
You can break them, but if you do you should have a good reason for it.</li>
</ul> </ul>
<p>TODO: Mention why Rust is a bit special - functional elements, type system,
borrow checker</p>
</main> </main>

31
print.html
View File

@ -151,26 +151,27 @@ are generically applicable.</p>
<p>Design patterns are a collection of reusable and tested solutions to <p>Design patterns are a collection of reusable and tested solutions to
recurring problems in engineering. They make our software more modular, recurring problems in engineering. They make our software more modular,
maintainable, and extensible. Moreover, these patterns provide a common maintainable, and extensible. Moreover, these patterns provide a common
language for developers to use, making them an excellent tool for effective language for developers, making them an excellent tool for effective
communication when problem-solving in teams.</p> communication when problem-solving in teams.</p>
<h2 id="design-patterns-in-rust"><a class="header" href="#design-patterns-in-rust">Design patterns in Rust</a></h2> <h2 id="design-patterns-in-rust"><a class="header" href="#design-patterns-in-rust">Design patterns in Rust</a></h2>
<p>There are many problems that share the same form. <p>Rust is not object-oriented, and the combination of all its characteristics,
Due to the fact that Rust is not object-oriented, design patterns vary with such as functional elements, a strong type system, and the borrow checker,
respect to other object-oriented programming languages. makes it unique.
While the details are different, since they have the same form they can be Because of this, Rust design patterns vary with respect to other
solved using the same fundamental methods:</p> traditional object-oriented programming languages.
That's why we decided to write this book. We hope you enjoy reading it!
The book is divided in three main chapters:</p>
<ul> <ul>
<li><a href="./patterns/index.html">Design patterns</a> are methods to solve common problems <li><a href="./idioms/index.html">Idioms</a>: guidelines to follow when coding.
when writing software.</li> They are the social norms of the community.
<li><a href="./anti_patterns/index.html">Anti-patterns</a> are methods to solve these same You should break them only if you have a good reason for it.</li>
common problems. However, while design patterns give us benefits, <li><a href="./patterns/index.html">Design patterns</a>: methods to solve common problems
when coding.</li>
<li><a href="./anti_patterns/index.html">Anti-patterns</a>: methods to solve common problems
when coding.
However, while design patterns give us benefits,
anti-patterns create more problems.</li> anti-patterns create more problems.</li>
<li><a href="./idioms/index.html">Idioms</a> are guidelines to follow when coding.
They are social norms of the community.
You can break them, but if you do you should have a good reason for it.</li>
</ul> </ul>
<p>TODO: Mention why Rust is a bit special - functional elements, type system,
borrow checker</p>
<div style="break-before: page; page-break-before: always;"></div><h1 id="translations"><a class="header" href="#translations">Translations</a></h1> <div style="break-before: page; page-break-before: always;"></div><h1 id="translations"><a class="header" href="#translations">Translations</a></h1>
<ul> <ul>
<li><a href="https://fomalhauthmj.github.io/patterns/">简体中文</a></li> <li><a href="https://fomalhauthmj.github.io/patterns/">简体中文</a></li>

2
searchindex.js
View File

File diff suppressed because one or more lines are too long

2
searchindex.json
View File

File diff suppressed because one or more lines are too long