@@ -55,13 +55,17 @@ Attendees Present:
55
55
* Eugene Burmako ([ @xeno-by ] ( github.com/xeno-by ) ), EPFL
56
56
* Andrew Marki ([ @som-snytt ] ( github.com/som-snytt ) ), independent
57
57
* Josh Suereth ([ @jsuereth ] ( github.com/jsuereth ) ), Google
58
+ * Dmitry Petrashko ([ @DarkDimius ] ( github.com/DarkDimius ) ), as a guest
58
59
* Jorge Vicente Cantero ([ @jvican ] ( github.com/jvican ) ), Process Lead
59
60
61
+ ## Guests
62
+ * Dmitry Petrashko ([ @DarkDimius ] ( github.com/DarkDimius ) ), EPFL (guest)
63
+
60
64
## Proceedings
61
65
### Opening Remarks
62
66
As acting Process Lead, Jorge Vicente Cantero conducted the meeting, made the
63
67
opening remarks, and introduced the guest Dmitry, who was present to help
64
- discuss his proposal for an improved lazy val initialization (SIP-20).
68
+ discuss the proposal for an improved lazy val initialization (SIP-20).
65
69
66
70
### Scala Improvement Proposals
67
71
#### Proposal SIP-25: Trait Parameters proposed by Martin Odersky
@@ -131,17 +135,17 @@ be resolved before resuming its evaluation.
131
135
revisit the support of async/await in try/catch blocks. When that's considered,
132
136
this SIP should be reopened and and it should see another round of discussion.
133
137
134
- #### Proposal SIP-20: Improved lazy val initialization by Dmitry Petrashko
135
- Sebastien reviews the SIP and asks Dmitry, present in the meeting, to correct
138
+ #### Proposal SIP-20: Improved lazy val initialization presented
139
+ Sébastien reviews the SIP and asks Dmitry, present in the meeting, to correct
136
140
him if he's wrong. He agrees that the SIP is desirable but he's unsure about the
137
141
benchmarks and which of the proposals is faster. Dmitry explains that the
138
- benchmarks are in the repo, and that in the best case the initialization doesn’t
139
- need synchronization.
140
-
141
- He also recommends the author to include more documentation.
142
+ benchmarks are in the repository. Sébastien also points out that there's an
143
+ implementation missing for scalac, and recommends the author to include more
144
+ documentation..
142
145
143
- ** Outcome** : Dmitry volunteers to provide an implementation in three months. The
144
- Process Lead schedules the next iteration by October 2016.
146
+ ** Outcome** : For the next itearation, the reviewer suggests that the SIP should
147
+ have an updated specification, implementation and benchmarks. The Process Lead
148
+ schedules the next iteration by October 2016.
145
149
146
150
#### Proposal SIP-27: Trailing Commas
147
151
Eugene Burmako, who also reviewed this recently submitted SIP, explains what the
0 commit comments