The compiler does understand the exhaustiveness of if ... else ... : https://play.golang.org/p/PAcg9oUAxA
Can you post some code to highlight the problem you're having? On 14 January 2017 at 21:31, Eric Brown <edb1...@gmail.com> wrote: > Using go, when I create a function with a return... and that function uses > an if... else... condition w/ the return being passed under each, the > compiler still throws an error 'missing return at end of function'? I can > put a return at the end of the function, but it will never get to that > point because of this condition. Is that expected, or could I be doing > something different to prevent this outcome? Not that it matters... but I > hate just having random returns at the bottom of functions that don't do > anything other than satisfy this issue. > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
