search for: quasiquot

Dear R Users, nofrills (0.2.0) has been published on CRAN: https://cran.r-project.org/package=nofrills This lightweight package provides `fn()`, a compact variation of the usual syntax of function declaration, in order to support tidyverse-style quasiquotation of a function?s arguments and body. Aside from enabling a shorter but fully general syntax for function declarations, the main benefit of `fn()` is its ability to create _pure_ functions via quasiquotation, which is tricky to guarantee in base R, due to the mutability of bindings in a functio...

Michael Lawrence (as last in long series of posters)... > Yes, it would bind the language object to the environment, like an > R-level promise (but "promise" of course refers specifically to just > _lazy_ evaluation). > > For the uqs() thing, expanding calls like that is somewhat orthogonal > to NSE. It would be nice in general to be able to write something like >

...than when linking already prelinked big *.o file. There are, perhaps, some confusions related to what GHC *runtime* linker is. GHC runtime linker goes out into the scene when either GHC is used interactively, or GHC encounters the code which it has to execute at compile time (Template Haskell/quasiquotations). Thus GHC compiler must link some external code during it's own run time. HTH. Cheers, Kyra

...e of people > who are writing fairly esoteric functions (which might then be used by > many)? If the later, it seems undesirable to me. I accidentally responded off list to Michael, but I think there are three legs to "tidy" style of NSE: 1) capturing a quosure from a promise 2) quasiquotation (unquote + unquote-splice) 3) pronouns, so you can be explicit about where a variable should be looked up (.data vs .end) These are largely orthogonal, but I don't think you can solve the most important NSE problems without all three. Just having 1) in base R would be a big step forward....

TL;DR: I'm trying to evaluate if LLD can be used with GHC (Glasgow Haskell Compiler) on Windows. Haskell binary code is usually deployed in "packages". A package typically provides static library(ies) and optionally – shared library(ies) and/or prelinked ('ld -r') object file. The latter is the best way to satisfy GHC runtime linker, since it requires no separate