On Mon, Mar 4, 2024 at 11:32 AM Mike Schinkel <m...@newclarity.net> wrote:
>
...
> 4. Relax the allowable values that can be assigned to a `const` to include
> values that can be fully determined at compile time such as `const April =
> [1]byte{4}` thus allowing `const` and
> types of subtypes `struct`, `map`, array, and/or slices to be used as
> pseudo-enums.
...
> P.S. Seems to me that #4 might be the simplest way forward as it would allow
> for creation of types that cannot be represented as their literal subtype
> value to pass as a parameter to a `func`, and it would not require any new
> keywords or concepts added to Go the language, or at least I don't think it
> would?
>
> Is there any reason Go could not relax the allowable values for const to be
> able to support constructs that can be determined at runtime such as `const
> April = [1]byte{4}`?
I think this is https://go.dev/issue/6386.
There are subtleties. The simple version only works if the variable
can be declared and initialized in the same statement. That isn't
alway feasible, which is why init functions exist. It absolutely
prohibits circular data structures, which could be limiting. But
anything else requires some way to separate the declaration from the
initialization while still prohibiting the value from changing after
initialization.
Ian
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcV0YnFTzCGGANTOQ-ZTXb2gAiXUnXRbH1_P%3D1Qz4hH_AQ%40mail.gmail.com.
