Understood - but the compiler already determines constants - determining the condition is a constant to avoid the current compiler error wouldn’t require an optimization. It seems that a constant false might also be reported as an error as an unreachable code block. On Oct 12, 2024, at 10:04 AM, Ian Lance Taylor <i...@golang.org> wrote: -- 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/024E1FB8-CA78-4F2A-90C9-CFD5C9E2DAC0%40ix.netcom.com. |
- [go-nuts] for mystery Pierpaolo Bernardi
- Re: [go-nuts] for mystery robert engels
- Re: [go-nuts] for mystery Ian Lance Taylor
- Re: [go-nuts] for mystery Cleberson Pedreira Pauluci
- Re: [go-nuts] for mystery Cleberson Pedreira Pauluci
- Re: [go-nuts] for mystery Cleberson Pedreira Pauluci
- Re: [go-nuts] for mystery Pierpaolo Bernardi
- Re: [go-nuts] for mystery Robert Engels
- Re: [go-nuts] for mys... Ian Lance Taylor
- Re: [go-nuts] for... Robert Engels
- Re: [go-nuts] for... 温博格
- Re: [go-nuts] for... Robert Engels
- Re: [go-nuts] for... Ian Lance Taylor
- Re: [go-nuts] for... Robert Engels