search for: zeallot

...that might not otherwise be detected * a character vector containing a list of variables referenced that might not otherwise be detected * expression e with potentially "offending" elements removed, which will then be processed by the rest of the checking code Then, say, 'zeallot' could implement zeallot::zeallot_assign_detect(), and a package developer using it could put utils::alternativeAssignment("%<-%", zeallot::zeallot_assign_detect) in their .onLoad() function. Similarly, users of 'dotty' could set up callbacks for all standard assignment o...

...tected > * a character vector containing a list of variables referenced that > might not otherwise be detected > * expression e with potentially "offending" elements removed, which > will then be processed by the rest of the checking code > > Then, say, 'zeallot' could implement zeallot::zeallot_assign_detect(), > and a package developer using it could put > > utils::alternativeAssignment("%<-%", zeallot::zeallot_assign_detect) > > in their .onLoad() function. Similarly, users of 'dotty' could set up > callbacks...

...come back to the issue of being annoyed by R not supporting multiple assignment out of the box like Matlab, Python and julia. e.g. something like A, C, Q, R = init_matrices(X, Y, Z) would be a great addition to the language. I know there are several workarounds such as the %<-% operator in the zeallot package or my own %=% operator in collapse, but these don't work well for package development as R CMD Check warns about missing global bindings for the created variables, e.g. I would have to use A <- C <- Q <- R <- NULL .c(A, C, Q, R) %=% init_matrices(X, Y, Z) in a package, whi...

...gt; > looking for such usages in your package, and calling > > globalVariables() > > so that R CMD check doesn't warn. In theory, a similar technique > > would > > be applicable to other packages defining similar operators > (zeallot, > > collapse). > > > > Obviously, globalVariables() is a very heavy hammer to swing for > > this > > issue, but you might consider the benefits worth the tradeoffs. > > > > Best, > > Kevin > > &gt...

...g annoyed by R not supporting multiple assignment out of > the box like Matlab, Python and julia. e.g. something like > > A, C, Q, R = init_matrices(X, Y, Z) > > would be a great addition to the language. I know there are several > workarounds such as the %<-% operator in the zeallot package or my own %=% > operator in collapse, but these don't work well for package development as > R CMD Check warns about missing global bindings for the created variables, > e.g. I would have to use > > A <- C <- Q <- R <- NULL > .c(A, C, Q, R) %=% init_matric...

...e package. The 'dotty' package includes a function 'dotify()' which automates looking for such usages in your package, and calling globalVariables() so that R CMD check doesn't warn. In theory, a similar technique would be applicable to other packages defining similar operators (zeallot, collapse). Obviously, globalVariables() is a very heavy hammer to swing for this issue, but you might consider the benefits worth the tradeoffs. Best, Kevin On Sat, Mar 11, 2023 at 2:53?PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > On 11/03/2023 4:42 p.m., Sebastian Mar...

...g multiple assignment out of > > the box like Matlab, Python and julia. e.g. something like > > > > A, C, Q, R = init_matrices(X, Y, Z) > > > > would be a great addition to the language. I know there are several > > workarounds such as the %<-% operator in the zeallot package or my own > %=% > > operator in collapse, but these don't work well for package development > as > > R CMD Check warns about missing global bindings for the created > variables, > > e.g. I would have to use > > > > A <- C <- Q <- R <- N...

...'dotty' package includes a function 'dotify()' which automates > looking for such usages in your package, and calling globalVariables() > so that R CMD check doesn't warn. In theory, a similar technique would > be applicable to other packages defining similar operators (zeallot, > collapse). > > Obviously, globalVariables() is a very heavy hammer to swing for this > issue, but you might consider the benefits worth the tradeoffs. > > Best, > Kevin > > On Sat, Mar 11, 2023 at 2:53?PM Duncan Murdoch <murdoch.duncan at gmail.com> > wrote: &...

Kia Ora > Although I'm not sure what problem it would solve... Given that you asked, I was interested in writing a multiple assignment function as a replacement function, so something like: massign (x, y, z) = construct.some list () Obviously, that's not possible. Probably the best example I can think of is converting cartesian coordinates to polar coordinates. Then we might have

On Friday, 26 June 2020 10.47.13 WEST I?aki Ucar wrote: > I used bcond locally and wrongly assumed that fedpkg build would > support --with BCOND and --without BCOND. Instead, the way to activate > it is to change to "%bcond_with check" and then revert to > "%bcond_without check". The only difference with bootstrap is that > "bootstrap" is recognized

...gt; > the box like Matlab, Python and julia. e.g. something like > > > > A, C, Q, R = init_matrices(X, Y, Z) > > > > would be a great addition to the language. I know there are several > > workarounds such as the %<-% operator in the zeallot package or > my own %=% > > operator in collapse, but these don't work well for package > development as > > R CMD Check warns about missing global bindings for the created > variables, > > e.g. I would have to use > > > &...

...otify()' which automates > looking for such usages in your package, and calling > globalVariables() > so that R CMD check doesn't warn. In theory, a similar technique > would > be applicable to other packages defining similar operators (zeallot, > collapse). > > Obviously, globalVariables() is a very heavy hammer to swing for > this > issue, but you might consider the benefits worth the tradeoffs. > > Best, > Kevin > > On Sat, Mar 11, 2023 at 2:53?PM...

...* R-tufte * R-tweenr * R-udunits2 * R-unitizer * R-units * R-unix * R-usethis * R-utf8 * R-uuid * R-V8 * R-vctrs * R-viridisLite * R-waveslim * R-wavethresh * R-webp * R-webutils * R-whisker * R-whoami * R-widgetTools * R-withr * R-xfun * R-XML * R-xml2 * R-xopen * R-xtable * R-XVector * R-yaml * R-zeallot * R-zoo * libsbml * libsedml * libnuml * shogun == Contingency Plan == * Contingency mechanism: The side tag will not be merged, or if a side tag is deemed unnecessary, the generator will not be installed, and any built packages will be re-built without it. * Contingency deadline: Beta Freeze *...

On 11/03/2023 4:42 p.m., Sebastian Martin Krantz wrote: > Thanks Duncan and Ivan for the careful thoughts. I'm not sure I can > follow all aspects you raised, but to give my limited take on a few: > >> your proposal violates a very basic property of the language, i.e. that all statements are expressions and have a value. > What's the value of 1 + (A, C =