I updated https://github.com/golang/go/issues/31076 to reflect the comments
here.
Thank you both.
On Fri, Mar 29, 2019 at 9:57 AM Ian Lance Taylor wrote:
> On Thu, Mar 28, 2019 at 11:17 PM Jan Mercl <0xj...@gmail.com> wrote:
> >
> > The Compatibility section of the proposal says: "I think that
On Thu, Mar 28, 2019 at 11:17 PM Jan Mercl <0xj...@gmail.com> wrote:
>
> The Compatibility section of the proposal says: "I think that this would
> break no existing code, as a user function invocation untyped(EXPR) is not at
> present allowed in constant specifications."
>
> It's true that user
Very helpful. Thank you. I will edit my proposal based on this.
On Thu, Mar 28, 2019 at 11:17 PM Jan Mercl <0xj...@gmail.com> wrote:
> The Compatibility section of the proposal says: "I think that this would
> break no existing code, as a user function invocation untyped(EXPR) is not
> at
The Compatibility section of the proposal says: "I think that this would
break no existing code, as a user function invocation untyped(EXPR) is not
at present allowed in constant specifications."
It's true that user function cannot be called in a constant expression. But
conversion to a user