On Fri, May 31, 2019 at 3:07 PM Kenton Varda <[email protected]> wrote:

>
>> With Elm and Haskell, I believe the only layer of namespacing that's
>> provided is the module name which is why both Ian and I gravitated to it
>> initially.
>>
>
> Are you saying Elm and Haskell don't provide any way to declare aliases?
> That seems surprising to me.
>
>
Note that Prasanth's example aliases a module that's at an intermediate
point in the nested hierarchy. I doubt that Haskell would let you do
something like:

  type Global = Pipeline'Stage'Worker'Global;
  ...
  case Global'Value'JSON: ...
  case Global'Value'NUMBER: ...

(Hm... or maybe something that could in fact work, but would require the
code generator to provide in each module type aliases to all types in that
module's "child" modules? Even so, I suspect that would not be very
practical.)

-- 
You received this message because you are subscribed to the Google Groups 
"Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/capnproto.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/capnproto/CABR6rW-FzAB_gjGNjiM3BAdGYEH46Pp5ue61BdQ44Z0mJPVw8w%40mail.gmail.com.

Reply via email to