ot to criticise your work which has its unique strengths, but to
state the obvious: these strengths are best discussed without passion
based on factually accurate descriptions.
[1]
https://developer.r-project.org/Blog/public/2021/03/12/windows/utf-8-toolchain-and-cran-package-checks/index.ht
start today, one could imagine removing.
But any change to semantics is really hard to implement by
source to source translation. My guess is that before you know it
you will have a very different language that runs extremely slowly.
Jan Vitek, Professor
Computer Science,
Northeastern University
Everything is possible. One can compile C++ into JavaScript.
But why?
> On Mar 4, 2019, at 6:28 PM, Abs Spurdle wrote:
>
> It may be possible to create an R-like programming language that
> transcompiles into R code (or otherwise constructs R objects and calls
> R functions).
>
> I'm not sure
>
> I think there's a bit of that flavour here:
>
> vec_c(factor("a"), Sys.Date())
> #> Error: No common type for factor and date
>
> This isn't a type system imposed by the language, but I don't think
> that's a reason not to call it a type system.
All I am saying is that without a clear def
> I'm now confident that I
> can avoid using "type" by itself, and instead always use it in a
> compound phrase (like type system) to avoid confusion. That leaves the
> `.type` argument to many vctrs functions. I'm considering change it to
> .prototype, because what you actually give it is a zero-l
Konrad are the contacts there.
Best,
jan
Jan Vitek, Professor
Computer Science,
Northeastern University
> On Jan 3, 2018, at 7:18 PM, Peter Meilstrup wrote:
>
> For 2), it is not exposed in R's standard library but it is exposed in
> the Rinternals API. A promise
