<p dir="ltr"><br>
Le 26 nov. 2014 16:08, "Jesper Cockx" <<a href="mailto:Jesper@sikanda.be">Jesper@sikanda.be</a>> a écrit :<br>
><br>
> I think this would be a very nice thing to reduce the verbosity of using universe polymorphism. A few remarks:<br>
><br>
> - If I understand correctly, a telsyntax statement would always contain exactly one visible argument plus any number of hidden and instance arguments before and after? This looks very similar to the idea Andreas proposed in Tallinn for changing the internal representation of hidden function types. So your proposal could be seen as a concrete syntax for this new internal representation.</p>
<p dir="ltr">Yes, that seems right. I haven't really followed the discussion on grouping of arguments in Tallinn, but it does sound close.</p>
<p dir="ltr">> - Do you want (A B C : Type) to be translated to {i : Level} (A : Set i) {j : Level} (B : Set j) {k : Level} (C : Set k), or to {i j k : Level} (A : Set i) (B : Set j) (C : Set k)? I usually write the latter, though the former is more consistent with the idea of grouping hidden arguments with a visible argument.</p>
<p dir="ltr">The advantage of the later is that you can factor the three Level arguments, so it's shorter when you have to write it by hand, but it would make much more sense to have it translated to the former.</p>
<p dir="ltr">> - There is a way to make sense of having Type and Group as the return type of a function: "f : ... -> Type" just stands for "f : ... -> Set _", and "g : ... -> Group0" stands for "g : ... -> Set", but using g also brings a term of type "GroupStr (g ...)" into scope for instance resolution. Then you could make (A : Set) a synonym for {i : Level} (A : Set i) instead of (A : Set0), so that functions that look non-level-polymorphic can actually be used at any level.</p>
<p dir="ltr">That makes sense for postulates for instance, but not for function definitions, if you want to define a function of type Group -> Group, then you have to provide the group structure on the result and it might be nontrivial.</p>
<p dir="ltr">> On Wed, Nov 26, 2014 at 2:33 PM, Guillaume Brunerie <<a href="mailto:guillaume.brunerie@gmail.com">guillaume.brunerie@gmail.com</a>> wrote:<br>
>><br>
>> Hello all,<br>
>><br>
>> As is well known, it’s currently a bit annoying to use universe<br>
>> polymorphism in Agda because instead of writing<br>
>><br>
>> f : (A B C : Type) -> …<br>
>><br>
>> you have to write<br>
>><br>
>> f : {i j k : Level} (A : Set i) (B : Set j) (C : Set k) -> …<br>
>><br>
>> Would it be a good idea to make the first one a syntactic sugar for<br>
>> the second one?<br>
>> I’m thinking about adding a "telsyntax" keyword, such that you can<br>
>> write for instance<br>
>><br>
>> telsyntax {i : Level} (X : Set i) = (X : Type)<br>
>><br>
>> and then (A B C : Type) (in a telescope) would be automatically translated into<br>
>><br>
>> {i : Level} (A : Set i) {j : Level} (B : Set j) {k : Level} (C : Set k)<br>
>><br>
>> And this is not just about universe management, but it would also be<br>
>> very useful when using instance arguments. For instance if a group is<br>
>> a type (of level 0, say) with a group structure (which will be found<br>
>> by instance search), and you want to write a function taking three<br>
>> groups as arguments you have to write<br>
>><br>
>> g : (G H K : Set) {{_ : GroupStr G}} {{_ : GroupStr H}} {{_ :<br>
>> GroupStr K}} -> …<br>
>><br>
>> But you could say instead<br>
>><br>
>> telsyntax (G : Set) {{_ : GroupStr G}} = (G : Group0)<br>
>> g : (G H K : Group0) -> …<br>
>><br>
>> And of course you can combine the two, if groups can be at any<br>
>> universe level then the following:<br>
>><br>
>> telsyntax {i : Level} (G : Set i) {{_ : GroupStr G}} = (G : Group)<br>
>> g : (G H K : Group) -> …<br>
>><br>
>> would be a shorthand for<br>
>><br>
>> g : {i j k : Level} {G : Set i} {H : Set j} {K : Set k} {{_ :<br>
>> GroupStr G}} {{_ : GroupStr H}} {{_ : GroupStr K}} -> …<br>
>><br>
>> which is much less readable and annoying to write.<br>
>><br>
>> One drawback (in the case of universe levels) is that you don’t have<br>
>> access to the level anymore, but I don’t think that would really be a<br>
>> problem, and you still can make the levels explicit if you need to.<br>
>> Another drawback is that when writing (A : Type) or (G : Group) in a<br>
>> telescope, it makes it look like Type and Group are types, but it’s<br>
>> not the case so it could be confusing (for instance you can’t end a<br>
>> function with "-> Group"). If that’s indeed too confusing, maybe we<br>
>> could use a different notation than a colon, to make it clear that<br>
>> it’s just syntactic sugar (on the other hand, it looks nice with a<br>
>> colon).<br>
>><br>
>> What do you think?<br>
>><br>
>> Guillaume<br>
>> _______________________________________________<br>
>> Agda mailing list<br>
>> <a href="mailto:Agda@lists.chalmers.se">Agda@lists.chalmers.se</a><br>
>> <a href="https://lists.chalmers.se/mailman/listinfo/agda">https://lists.chalmers.se/mailman/listinfo/agda</a><br>
><br>
><br>
</p>