Brodie Gaslam
Brodie Gaslam
Add instructions for utils::globalVariables() for the ., figure out if there is some way the package can inherit that declaration for its checks. Magrittr issue for context: https://github.com/tidyverse/magrittr/issues/29
@moodymudskipper: https://moodymudskipper.github.io/typed/
We write `(char *)` pointers to a malloc bloc that is `double` aligned; need to make sure the assumption that the alignment is compatible is true, e.g. in startup assertions....
@dselivanov asks: > @BrodieGaslam do you think it is feasible to make something similar to https://pydantic-docs.helpmanual.io on top of vetr? Looks like a good idea to signal classed conditions, especially...
Clearly `qassert` triggers way fewer GCs: ``` > gcinfo(TRUE) [1] TRUE > simple_vet nums for(i in 1:5e4) simple_vet(nums) Garbage collection 206 = 155+20+31 (level 0) ... 35.8 Mbytes of cons...
In success case, we should not need to match.call the user call. Can it be avoided? More generally, the `match.call` used within functions should be avoidable by using a wrapper...
``` > val.toks vet(val.toks[[1]], 1L) [1] "`1L` should be type \"language\" (is \"integer\")" ```
Something is wrong with how windows is handling the out of BMP unicode code points. For example, "\U0001F600" shows up as "" on windows, basically reading the long form U...
Add a mode that just returns FALSE on failure instead of constructing an error message in order to have similar performance in success and failure (@franknarf1).
Several things to look into: * Check in on valaddin * Links to https://github.com/keynmol/valdeece * validtar? (couldn't find this)