3 ms·
That's fair enough. I knew implementing it this way would ruffle a few feathers, and I totally understand why. I too would love to see ("a","b"), and proper p
by louthy 12y ago
That's fair enough. I knew implementing it this way would ruffle a few feathers, and I totally understand why. I too would love to see ("a","b"), and proper pattern matching... and ..
This was a weekend project that kind of grew over the past few days. Initially I wasn't going to make everything lowercase, but I started thinking about the fact that a lot of these functions are now essentially global and the potential for clashes in real code. So I felt having a core set of useful functions that look more like the lowercase keywords of C# rather than library methods would work better. It definitely won't be everybody's cup of tea though.
- martijn_himself 12y agoI realise my comment is probably a bit too negative- I really like your ideas (especially the Option type). Things like Tuple<T1,T2,T3> etc. make me wonder if we would not all be better off though if we just started using F#... although I still like C#.
- louthy 12y ago> I realise my comment is probably a bit too negative Not at all, you're entitled to your opinion. Whatever works for you :) > we would not all be better off though if we just started using F#... although I still like C# That would be nice. Unfortunately it's not always quite as easy as that. At least in my corner of the world!