Davy Landman
Davy Landman
> > > for reference, these are the jars we will force everybody that uses Rascal to depend on for their own Rascal projects: True, but using shading (which we...
> But let's not do this for the JDT. It's way way to complex You are right, for jdt, way to dangerous (I did use the 😈). But for other...
Maybe we should only print it if in the end it couldn't find a tpl? Since often it just shows where it's looking.
Agreed, it's all about that scheme. But this is a user facing variant of it, clicking on the link in the terminal brings you to the wrong version of it....
we could also add the context of the lib in the uri, so that you know that `lib://typepal-a` should be interpreted in the context of the a project? that would...
fine with me. you seem to have an idea of how to fix this.
Are you sure it's not related to #1802 ? Else it's an awful coincidence.
Just want to write down that this is a much larger issue, that will entail some significant rework on how we work with datetimes in vallang. But want to leave...
I mean, that if I write ``` rascal> $2020-01-01T00:00:00$ ``` and get back the following value: ``` $2019-31-12T23:00:00Z$ ``` that is a lot more confusing than getting back: ``` $2020-01-01T00:00:00+01:00$...
I like the fact that we return a different way to consume an IString (instead of just a iterator). It does allow people to introduce unicode bugs again. (The IString...