@cairdcoinheringaahing I will be accepting nominations for languages to be used might wanna fix the wording, as it seems like you are restricting all available langs to the nominated ones
@BlackCap did you really edit in a different color for yourself? :P
I guess you could make a runtime that transpiles it into all the different languages, fires up several interpreters, and then essentially sends them commands to execute code with certain values
@SocraticPhoenix By "not supported" they mean "it's there, but there are a shit ton of warnings you'll get telling you it's a terrible idea, and you need intentionally obscure flags."
Ok, question: If I need to store a list of widgets associated with animations, given multiple animations can be associated with a single widget, which of these is preferable? HashMap<Widget, List<Animation>>, with a list of animations for each widget, or a List<(Widget, Animation)>, with each Widget-Animation association as it's own entry?
OK, quick question: if you had choice over the label of a range to use for something, that you had to use, would you choose a range that was 0..100, or -20..40?
@SocraticPhoenix I think you should use a HashMap for now and not worry about it, then when you're done try LinkedHashMap and see if it gets noticably faster.
@Phoenix hmm.. I wasn't thinking about speed - I just figured it made more sense that if you declare a map literal and iterate over it, you get the entries in order...
@Phoenix true.. the only place I've ever used LinkedHashMap is in the ordering of configuration properties... so they write to file in the same order...
C# 7 technically only supports up to size 8 under the hood, but then it does magic where the 8th type is another tuple, and then the tuples get "flattened" in the actual code.