search for: getas

Hi, The code below creates a value, x$a, which depending on how you access it evaluates to its initial value, or to what it's been changed to. The last two lines should, I would have thought, evaluate to the same value, but they don't. f <- function () { x <- NULL; x$a <- 0; x$get.a <- function () { x$a; }; x$increment.a <- function () { x$a <<- x$a + 5;

...he Static > Analyzer, the SVal hierarchy. > > So, Ted, how objectionable would it be for me to introduce something > like (names subject to adjustment): > > template<typename T> > T SVal::castAs(); > > template<typename T> > llvm::Optional<T> SVal::getAs(); > > (the implementations of these functions might involve invoking private > FooSVal(SVal) ctors in each SVal derived type - so adding a bit of > boilerplate ctors to all those classes) > > and replace "cast<FooSVal>(bar)" with "bar.castAs<FooSVal>(...

Hi there, I''d like to choose between an "static" and "dynamic" access of a reference class field, say ''a''. myObj <- getRefClass("Blabla")$new() Static: myObj$a Dynamic: myObj$a.get() where the function retrieves the data from a database (or some other location), stores it to a buffer and

...;s another more pervasive use of this pattern in the Static Analyzer, the SVal hierarchy. So, Ted, how objectionable would it be for me to introduce something like (names subject to adjustment): template<typename T> T SVal::castAs(); template<typename T> llvm::Optional<T> SVal::getAs(); (the implementations of these functions might involve invoking private FooSVal(SVal) ctors in each SVal derived type - so adding a bit of boilerplate ctors to all those classes) and replace "cast<FooSVal>(bar)" with "bar.castAs<FooSVal>()" and dyn_cast with getA...

+ Erik, who implemented DR1579 Originally, I had the warning similar to GCC's warning, but took it out due to not having DR1579 implemented in clang (warning changed in r243594) Erik in r274291 implemented DR1579, although PR27785 didn't mention anything about std::move It looks like what's happening is that Clang and GCC handles the return differently. Clang needs the std::move

I've been using winbind successfully for awhile now for user info (nothing in /etc/passwd), but today I tried to use it to pull group info, so I updated /etc/nsswitch.conf (RH 7.3) and then tried to add: valid users = @DOMAIN+group_name and now whenever I click on any folder (share) to open the cpu util goes up, and the connection hangs for awhile, and then eventually it times-out on the

Greetings, Say I have defined mp <- function(a) function(x) x^a f2 <- mp(2) and I would like to retrieve the "a" which is local to f2. Two options come to mind; get("a", envir=environment(f2)) eval(substitute(a), environment(f2)) I'm curious if one of these is preferred over the other in terms of efficiency, robustness, aesthetics, etc. Or perhaps

Hi all, i have a data set cintaining 14 columns and 11 rows. Rows represent single point and columns represent the parameter measured. I wiuld like to compare the data to see which are more alike. I used the cluster analysis, but now i ma wondering if there are some other methods, since the cluster analysis did not give me the result i like. I tried to use factanal() for factor analysis

Yes, we should produce this warning in C++11 mode too. (I could be misrecalling, but I think the rationale for the current behaviour is based on historical GCC behaviour.) On Sun, 16 Sep 2018, 10:04 David Blaikie via cfe-dev, < cfe-dev at lists.llvm.org> wrote: > Fair point made on that thread - that this is a DR, so technically the > std::move is pessimizing even in C++11 mode.

Hi, With help from Oleg we got the right patches applied and NFS working well. Maximum performance was about 60 MB/sec. Last week that dropped to about 12.5 MB/sec and I cannot find a reason. Lustre clients all obtain 100+ MB/sec on GigE. Each OST is good for 270 MB/sec. When mounting the client on one of the OSSs I get 230 MB/sec. Seems the speed is there. How can NFS and Lustre be tuned

https://bugzilla.mindrot.org/show_bug.cgi?id=2218 Bug ID: 2218 Summary: ProxyCommand as both a resolver and connector Product: Portable OpenSSH Version: 6.5p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at

On Thu, Nov 29, 2012 at 8:16 PM, Richard Smith <richard at metafoo.co.uk> wrote: > On Thu, Nov 29, 2012 at 7:43 PM, Eli Friedman <eli.friedman at gmail.com> > wrote: >> >> On Thu, Nov 29, 2012 at 3:49 PM, David Blaikie <dblaikie at gmail.com> wrote: >> > Moving to LLVM dev to discuss the possibility of extending the cast >> > infrastructure to

On Dec 16, 2018, at 11:44 AM, Stephen Kelly via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 25/11/2018 14:43, Stephen Kelly via llvm-dev wrote: >> However this is a proposal for more modern thinking regarding the permissiveness of auto in LLVM codebases. >> Currently the rule on the use of auto is here: > > Hi, > > Thanks for the input on this topic,

On Thu, Nov 29, 2012 at 7:43 PM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Thu, Nov 29, 2012 at 3:49 PM, David Blaikie <dblaikie at gmail.com> wrote: > > Moving to LLVM dev to discuss the possibility of extending the cast > > infrastructure to handle this. > > > > On Tue, Nov 20, 2012 at 5:51 PM, John McCall <rjmccall at apple.com> wrote:

Hi George, On Mon, Jan 2, 2017 at 10:41 AM, George Burgess IV <george.burgess.iv at gmail.com> wrote: > Thanks for the comments! > >> Have you considered changing our existing behavior to match GCC's >> builtin_object_size instead of adding a new parameter > > Yup! My issue with turning `i1 %min` into `i8 %flags` is that > __builtin_object_size would get