You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _sips/minutes/2020-03-13-sip-minutes.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Martin presented `@main` functions:
77
77
- Initialisation code in object can cause problems for thread safety.
78
78
- Because we have top level definitions, it makes perfect sense to allow program entrypoint to be method at the top level.
79
79
- What should the program be called? We use the `@main` annotation to capture the method name and create a wrapper class of the same name in the package containing the method.
80
-
- Also provide minimal commandline argument processing to map directly to method parameters, using the `FromDigits` type class.
80
+
- Also provide minimal commandline argument processing to map directly to method parameters, using the `FromString` type class.
81
81
82
82
#### Concerns with Commandline Argument Processing
83
83
@@ -111,7 +111,7 @@ Adriaan:
111
111
- Is `FromString` too general to use for CLI processing, it could make evolution harder if people use it for other cases.
112
112
- Lots of options for the problem of structuring unstructured data, such as `:` separated lists for class paths. A general type class is too basic for this situation.
113
113
- However, it is easier to make a local specific `FromString` just for CLI than in haskell where you must consider global importance.
114
-
- Agrees that whatever argument processing should be able to map directly to method arguments, but something more specialised than `FromDigits` should be used.
114
+
- Agrees that whatever argument processing should be able to map directly to method arguments, but something more specialised than `FromString` should be used.
115
115
- Alternatively the current proposal could go ahead, but removing hooks for extension in the StdLib.
116
116
117
117
Martin, addressing these concerns:
@@ -157,7 +157,7 @@ Guillaume:
157
157
158
158
#### Summary
159
159
160
-
The main concerns with the proposal are the interactions between the intended use case and the pressure it imposes on the Standard Library. If it is only intended for very simple ordered arguments then perhaps a pluggable `FromDigits` type class is too simple to include in the standard library. If the language should support more complicated processing, then `FromDigits` is too basic to be pluggable.
160
+
The main concerns with the proposal are the interactions between the intended use case and the pressure it imposes on the Standard Library. If it is only intended for very simple ordered arguments then perhaps a pluggable `FromString` type class is too simple to include in the standard library. If the language should support more complicated processing, then `FromString` is too basic to be pluggable.
161
161
162
162
In a straw poll the present members of the committee were in favour of having the `@main` annotation for program entry points, but perhaps someone could come up with a proposal for a more sophisticated processing solution.
163
163
@@ -177,7 +177,7 @@ Jamie:
177
177
178
178
Sébastien:
179
179
180
-
- In Scala it is rare to have concrete expected type, e.g. the left hand side of an operation.
180
+
- In Scala we often lack a concrete expected type, e.g. the left hand side of an operation.
181
181
- How well does this scale
182
182
- Concerns for loss of precision, e.g. different behaviour of adding different numeric types etc.
0 commit comments