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
Currently, required fields are defaulted to the "zero" value for that type. We should instead provide smart construction that checks at compile time whether all the required fields have been set properly.
Note that this is moot for proto3, which got rid of the concept of required fields altogether.
One possible, nebulously-described approach: for every datatype Foo, also define a Foo'Builder which is parametrized by the type of each required field (and which may be () if it's not set). This Foo'Builder can be an instance of Default (instead ofFoo), and we can provide lenses to build up its individual fields, as well as a class to "freeze" Foo'Builder into Foo once all its fields have been set.
The text was updated successfully, but these errors were encountered:
I'm not sure why, but in some cases it seems linking only works if *both* the
.so and the .dylib are present in /usr/local/lib. This may be due to a quirk
of how Bazel builds the library, and/or how ghc/stack load the library.
Currently, required fields are defaulted to the "zero" value for that type. We should instead provide smart construction that checks at compile time whether all the required fields have been set properly.
Note that this is moot for proto3, which got rid of the concept of required fields altogether.
One possible, nebulously-described approach: for every datatype
Foo
, also define aFoo'Builder
which is parametrized by the type of each required field (and which may be()
if it's not set). ThisFoo'Builder
can be an instance ofDefault
(instead ofFoo
), and we can provide lenses to build up its individual fields, as well as a class to "freeze"Foo'Builder
intoFoo
once all its fields have been set.The text was updated successfully, but these errors were encountered: