Sorry about the code styling, it could do with some work.
I liked some of the ideas here, but agree it's a shame to completely hide error handling rather than just make it simpler. There's an interesting discussion of Go error handling for Go 2 here with lots of proposals. For scripts I guess it's fine to panic in most cases (though I feel like sometimes you'd want to handle it gracefully and tell the user), but even just some simpler syntax like on one line this would be nice:
f, err := os.Create("hello.txt")
return on err { println(err) }I agree better to be explicit - I don't really like the spooky hidden errors in this proposed language. Fun to see people experimenting with different approaches though - I think it makes the tradeoffs a lot clearer when using go itself.