|
| taberiand wrote:
| I don't know Go, but this sounds analogous to .net solution /
| project files - is that kind of what this is?
| metaltyphoon wrote:
| Yes
| pstuart wrote:
| Now that Go has generics (and the workspace handling mentioned
| here) I think it's going to get down to complaining about verbose
| error handling...
| heavyset_go wrote:
| I like Java-style checked exceptions and Rust's Result enums,
| and my ideal error handling would be more verbose compared to
| Go's error handling.
| tmp_anon_22 wrote:
| I wonder how practical it would to implement much of Rust's
| error handling syntactic sugar in Golang. I'm sure a lot
| doesn't transfer over, but Rust seems to have learned a lot
| from other languages like Golang in this regard.
| obilgic wrote:
| it's going to get down to complaining about introducing
| generics way too late.
| malkia wrote:
| Wow. That's not a small thing to internalize. I guess if you use
| predominantly Go, then that's good and understanabdle, but if you
| have more languages in the mix (C/C++, Python, C#, Java, Rust),
| each of them have their own build ways and quirks (at least with
| Go/Rust/C# there is build single option (AFAIK)), but then do -
| do I need to clean now? Is this going to really get my latest
| change? Is the IDE going to see these new symbols, the debugger,
| etc.
|
| I know people like when their language comes with build system,
| but that creates a cost when that language/runtime has to be used
| with others...
| throwra620 wrote:
___________________________________________________________________
(page generated 2022-04-11 23:00 UTC) |