search for: geta

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 get...

...ostream> #include <memory> struct A { A(int) {} A() { std::cout << "empty constructor"; } A(const A&) { std::cout << "copy constructor\n"; } A(A&&) { std::cout << "move constructor\n"; } }; struct B { B(A a) {} }; A getA() { return A(1); } B run1() { A a = getA(); return std::move(a); } B run2() { A a = getA(); return a; } int main() { std::cout << "with move:\n"; run1(); std::cout << "no move:\n"; run2(); } On Tue, Sep 18, 2018 at 4:07 PM Richard Trieu <rtri...

...hangs for awhile, and then eventually it times-out on the client side, and the server logs initgroup errors. Anyone seen this? It is connecting to a rather large AD forest, and I'm told there are groups with 30+ users in them. When I do a winbind -g |wc -l I get about 63,210 entries before I geta 0c000233 error (I think that was it). I tried group enumeration on/off and that doesn't change anything. Anyone have other ideas? Dan

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

...s 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 but i geta an error saying that it can only be used on numerical data (which is odd since all i have is numerical data). For factanal i used this code : DFm<-read.csv("kemijaM.csv", sep=";", dec=".") # input data DF.m<-as.matrix(DFm)...

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

...ve as a resolver. For example, for the given name such command is supposed to returns the full name that is used for the key lookup and optionally the ip address and port to connect to. The drawback of this is that the proxy command may need to duplicate the functionality of a custom resolver as to geta fully qualified form the resolver may need to figure out what use to connect to that host. As a custom resolver may reintroduce the rogue DHCP server problem discussed in [1], I suppose the returned name should present on CanonicalDomains list. [1] - http://blog.djm.net.au/2014/01/hostname-canoni...

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