Comments (10)
In that issue the fact that these issues should be taken from that blog post is not clear in my opinion.
Anyway I prefer smaller issues with respect to big ones, because it is impossible to follow too many discussions at the same time. Maybe that issue could link to this one? 😅
from patterns.
Yeah, let's see how it develops.
from patterns.
awesome, thanks!
from patterns.
Related: https://github.com/rust-lang/api-guidelines/tree/master/src
from patterns.
Yeah, we don't want to overlap with the rust api guidelines (which is also linked in the killercup article).
Let's discuss each of those individually:
- Builder pattern
- Typestates/Session types (PR)
- Public type aliases
- Use conversion traits
- Laziness: Use Iterators
- Laziness: Take closures
- Custom traits for input parameters
- Extension traits
from patterns.
Should we close this in favour of #116 ? I copied everything needed from this issue over.
from patterns.
Agreed, discussions should still take place in smaller issues, it's an umbrella. i thought about opening an issue for each of the points in this issue actually. hence why i asked about closing. we could link from each of these issues to this one here to make clear, that there might be material taken from it
from patterns.
What you are suggesting is the opposite: too small issues 😂
I propose to keep the sub-issues as checklist (see the second comment) and split the discussion in different issues if and when needed :)
from patterns.
Yeah, or even better use the discussion board for discussing how to write the patterns and keep the issues clean for actual issues, what do you think?
from patterns.
It depends for what you mean with "actual issues".
I think "discussions" are still in beta and they are more meant for "stack overflow" kind of random questions.
I wouldn't force users to use discussions over issues to express concerns about the content of this book.
from patterns.
Related Issues (20)
- Floating Point Related Idioms HOT 1
- Add double panic mentioning for RAII guards HOT 1
- Clarify parts of Lenses and Prisms chapter HOT 11
- Borrow Checker Patterns HOT 2
- Clarify paragraph in Generics as Type Classes
- Clarify naming convention of `build()` in section 3.2.1 HOT 1
- Design Patterns, Strategy has unclear identifier `Context` and `run` mentioned. HOT 1
- View type
- Translations HOT 6
- Incorrect text in Command pattern description
- Translation: Persian HOT 5
- Is this example wrong ? HOT 1
- Printing the book should not inherit theme colours HOT 1
- Extract code into runnable Rust files HOT 4
- Translate: Vietnamese HOT 2
- Typo in idioms/coercion-arguments.md HOT 3
- Add pdf renderer and link rendered book
- Consistent Headline Capitalization? HOT 1
- Incompatible definition of Mutex::lock (or MutexGuard)
- Foo Bar (ad nauseam)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from patterns.