search for: baath

In November, we had a "bug repository conversation" with Peter Hagerty and myself: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16065 where the bug report title started with --->> "exists" is a bottleneck for dispatch and package loading, ... Peter proposed an extra simplified and henc faster version of exists(), and I commented > --- Comment #2

...t; I have already tested it a bit, but not yet committed to R-devel > > (the "R trunk" aka "master branch") because I'd like to get > > public comments {RFC := Request For Comments}. > > > > I don't like the name -- I'd prefer getIfExists. As Baath (2012, R > Journal) pointed out, R names are very inconsistent in naming > conventions, but lowerCamelCase is the most common choice. Second most > common is period.separated, so an argument could be made for > get.if.exists, but there's still the possibility of confusion with S3 &...

...simple to implement, > I have already tested it a bit, but not yet committed to R-devel > (the "R trunk" aka "master branch") because I'd like to get > public comments {RFC := Request For Comments}. > I don't like the name -- I'd prefer getIfExists. As Baath (2012, R Journal) pointed out, R names are very inconsistent in naming conventions, but lowerCamelCase is the most common choice. Second most common is period.separated, so an argument could be made for get.if.exists, but there's still the possibility of confusion with S3 methods, and users of...

...t; I have already tested it a bit, but not yet committed to R-devel > > (the "R trunk" aka "master branch") because I'd like to get > > public comments {RFC := Request For Comments}. > > > > I don't like the name -- I'd prefer getIfExists. As Baath (2012, R > Journal) pointed out, R names are very inconsistent in naming > conventions, but lowerCamelCase is the most common choice. Second most > common is period.separated, so an argument could be made for > get.if.exists, but there's still the possibility of confusion with S3 &...

...sted it a bit, but not yet committed to R-devel >> > (the "R trunk" aka "master branch") because I'd like to get >> > public comments {RFC := Request For Comments}. >> > >> >> I don't like the name -- I'd prefer getIfExists. As Baath (2012, R >> Journal) pointed out, R names are very inconsistent in naming >> conventions, but lowerCamelCase is the most common choice. Second most >> common is period.separated, so an argument could be made for >> get.if.exists, but there's still the possibility of con...

...> I have already tested it a bit, but not yet committed to R-devel > > (the "R trunk" aka "master branch") because I'd like to get > > public comments {RFC := Request For Comments}. > > > I don't like the name -- I'd prefer getIfExists. As Baath (2012, R > Journal) pointed out, R names are very inconsistent in naming > conventions, but lowerCamelCase is the most common choice. Second most > common is period.separated, so an argument could be made for > get.if.exists, but there's still the possibility of confusion with S3 &...

...ot yet committed to R-devel >>> > (the "R trunk" aka "master branch") because I'd like to get >>> > public comments {RFC := Request For Comments}. >>> > >>> >>> I don't like the name -- I'd prefer getIfExists. As Baath (2012, R >>> Journal) pointed out, R names are very inconsistent in naming >>> conventions, but lowerCamelCase is the most common choice. Second most >>> common is period.separated, so an argument could be made for >>> get.if.exists, but there's still the po...