I don't deal with a lot of ad-hoc data, but even when I do, that data usually needs strict validation, as it tends to not be very clean. Having things silently convert hides this and while it may make the code simpler, that code should have validation anyway, so it really won't be any more work in the long run (for me). Slight errors in data cause billion dollar bugs, after all. Maybe not in NLP though, so, again, we have different use cases.
But that's just me and obviously my priorities differ from yours. In any case, congratulations on building this, that's quite an achievement.
Nice!
As a source code reader I would much prefer to see at least a keyword or function call to make the casting explicit.
string s = cast 10; s += cast 20;
(I had the same reaction as the parent and think the language looks really cool otherwise)
i = int(s)+10;
Each type can be used as a "function" to create the object you like, which is basically what a cast is...
I'm building one too in Rust and there exist a very nice concept:
https://doc.rust-lang.org/std/convert/trait.From.html
Is the first time I see a blessed way into a lang to define conversions.
For example, to parse strings into int you need to say (in pseudo-code):
convert::From(String) -> Int //Or better convert::TryFrom
and suddenly you get the way to convert to strings into ints EVERYWHERE.Is amazing.
The key here is that is for much more than just basic stuff. You can do a lot of very convoluted things here, like Auto-Convert a vector of ints into a Zip compressed stream in one go.
----
The second things required is how avoid the boilerplate when dealing with data. If I read a file and need a lot of parsing and validation and need to be relaxed about this... how about the same thing between eager and lazy?
- Have "strict" by default and need to manually do
1->Str + "hello" + today->Str + ...
calls- Have a "auto-convert" when need to chain a lot of steps:
auto {
1 + "hello" + today + ...
}
this is nice because you can see where the " big dirty vicious beasts full of mistakes and traps" are in your code!In this example, I implement a join that takes a vector and transforms it into a string.
//type declaration
<joining:: vector -> string>
//The function itself
<joining(v) = x | x <- v>
println(joining(['a'..'z']));
Perl does this and it's a lot cleaner IMO. Whenever you see a "+" you can consider it an explicit numeric conversion of both arguments: https://codespeaks.blogspot.com/2007/09/ruby-and-python-over...
In fact, there is no dedicated numeric conversion operator in perl. The canonical "operator" for this is called the "0+" operator.
Python-style dynamic-typing and strictness is sort of the worst-of-both-worlds approach. Many times I've lost rarely-seen log messages to "cannot concatenate 'str' and 'int' objects" errors.
string s = 10; s += 20;
What I define is an operation within a string. The context is defined by the recipient variable. In the same way:
int i = 20; i += "30";
The variable "i" defines an integer context and therefore string 30 is considered in this case as a number.