Skip to content

Issues: alexandru/scala-best-practices

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

19 Open 14 Closed
19 Open 14 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[question] Usage of return
#64 opened Aug 7, 2019 by franklinchou
1
Usage of underscore
#59 opened Nov 14, 2018 by frgomes
explicit section/subsection numbers make it harder to contribute
#52 opened Mar 14, 2018 by wookietreiber
1
2
2.17 Nested case classes?
#43 opened Dec 12, 2016 by macalinao
1
Scala return actually throws NonLocalReturnControl[A] now
#42 opened Dec 8, 2016 by zhenglaizhang
Rule 5.1 needs a *good* example
#38 opened Jun 10, 2016 by ches
1
3.4. SHOULD be mindful of the garbage collector — Incorrect example
#36 opened Feb 22, 2016 by Aivean
2
Rule about updating a var for loops or conditionals
#34 opened Jan 9, 2016 by JGailor
17
Add a rule about best / bad practices for implicits and context bounds
#33 opened Jan 2, 2016 by staslev
7
Add rule on not doing TODO comments
#25 opened Aug 17, 2015 by alexandru
1
Use if-else vs pattern matching for booleans
#24 opened Aug 5, 2015 by smajithia76
8
2.6 issues
#19 opened Dec 3, 2014 by ejstrobel
2
Add rule on avoiding optional function parameters
#18 opened Nov 10, 2014 by alexandru
1
Rule 4.4 example
#17 opened Nov 3, 2014 by ramn
1
2.17. SHOULD NOT define case classes nested in other classes
#16 opened Nov 2, 2014 by muuki88
6
Add // bad example - for clearly marking bad code samples
#14 opened Oct 31, 2014 by alexandru
1
MUST NOT use capital letters but for the most important things
#12 opened Oct 31, 2014 by jrudolph
3
Rule 5.2 could mention possible memory leak
#11 opened Oct 31, 2014 by q42jaap
1
Rule 4.3 needs clarifications
#8 opened Oct 31, 2014 by alexandru
ProTip! no:milestone will show everything without a milestone.