search for: washy

...ite 'isMyConditionTrue()'? Or 'bool &x = I->isMyConditionTrue'? Or something else? I have no idea. Warnings and other things can help reduce the likelihood of this becoming a live bug, but it still makes the code harder to read IMO. This is exactly why I was making the wishy-washy statement about instance variables. This is the pattern that I tend to prefer: class Something { bool IsMyConditionTrue; … bool isMyConditionTrue() const { return IsMyConditionTrue; } } If you make instance variables be lower camel case, then you get serious conflict between ivars and met...

...ool &x = >> I->isMyConditionTrue'? Or something else? I have no idea. Warnings and >> other things can help reduce the likelihood of this becoming a live bug, >> but it still makes the code harder to read IMO. >> >> This is exactly why I was making the wishy-washy statement about instance >> variables. This is the pattern that I tend to prefer: >> >> >> class Something { >> bool IsMyConditionTrue; >> >> … >> >> bool isMyConditionTrue() const { return IsMyConditionTrue; } >> } >> >>...

...t; >> Compiled with -mfma -ffast-math, this generates fma(x, y, x). Even >> though this transform superficially appears to use distributivity, >> that’s somewhat debatable because the fma computes the whole result >> without any intermediate rounding, so it’s pretty wishy-washy to say >> that it’s been used here. > > It most definitely has been used here, because of inf/nan behavior. > > inf*(0 + 1) == inf > inf*0 + inf == nan > > (I actually fixed this bug in the past because it occurred in practice.) Thanks Nicolai and Steve for the initial...

Dear LLVM developers, I have a question on the fast-math floating-point optimizations applied by LLVM: Judging by the documentation at https://llvm.org/docs/LangRef.html#fast-math-flags I understood that rewriting with associativity and using reciprocal computations are possible optimizations. As the folklore description of fast-math is that it "applies real-valued identities", I

Hello R-devel, Approximately [*] the following CRAN packages make use of the pipe syntax in their source code or examples without depending on R >= 4.1: [1] "biplotEZ" "CaseBasedReasoning" "collinear" [4] "cubble" "disk.frame" "duckdbfs" [7] "eia" "feltr"

Thanks for looking into this and the patch. FWIW, there's an open PR18105 - "R CMD build: Add dependency on R >= 4.1.0 if code uses pipe symbol |>" for this (https://bugs.r-project.org/show_bug.cgi?id=18105). /Henrik On Thu, Jan 16, 2025 at 3:42?AM Ivan Krylov via R-devel <r-devel at r-project.org> wrote: > > Hello R-devel, > > Approximately [*] the

>>>>> Henrik Bengtsson writes: Thanks. Will take a look ... Best -k > Thanks for looking into this and the patch. FWIW, there's an open > PR18105 - "R CMD build: Add dependency on R >= 4.1.0 if code uses pipe > symbol |>" for this > (https://bugs.r-project.org/show_bug.cgi?id=18105). > /Henrik > On Thu, Jan 16, 2025 at 3:42?AM Ivan Krylov

>>>>> Kurt Hornik writes: Oh dear. Using a variant of Ivan's code, I seem to find 728 (!!!) CRAN packages which are missing their R >= 4.1 dependency. So clearly we need to do more about this than teach R CMD build to add the dependency ... Best -k >>>>> Henrik Bengtsson writes: > Thanks. Will take a look ... > Best > -k >> Thanks for

On May 2, 2008, at 2:23 PM, me22 wrote: [...] > I suppose the most important issue is what constitutes "observable > behavior". 1.9/6: «The observable behavior of the abstract machine is its sequence of reads and writes to volatile data and calls to library I/O functions. [ Footnote 6: An implementation can offer additional library I/O functions as an extension.

>>>>> Kurt Hornik writes: I just committed c8761[2-4] to the trunk which adds an internal utility for finding package code using the pipe or function shorthand, teaches R CMD build to add a dependency on R >= 4.1.0 as necessary, and teaches R CMD check to NOTE a missing dependency on R >= 4.1.0, based on Ivan's code. Currently, we seem to have about 1149 packages on

...ConditionTrue'? Or something else? I have no idea. Warnings and >>>> other things can help reduce the likelihood of this becoming a live bug, >>>> but it still makes the code harder to read IMO. >>>> >>>> This is exactly why I was making the wishy-washy statement about >>>> instance variables. This is the pattern that I tend to prefer: >>>> >>>> >>>> class Something { >>>> bool IsMyConditionTrue; >>>> >>>> … >>>> >>>> bool isMyCondition...

> If we are going to change how we name variables, I very much want them to > not collide with either type names or function names. My suggestion would be > "lower_case" names. > > This also happens to be the vastly most common pattern across all C++ coding > styles and C-based language coding styles I have seen. STL has "lower_case" functions, and exposes

Has anyone noticed this behavior: > library(ctest) Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library "J: \STATS\RW1000/library/ctest/libs/ctest.dll": LoadLibrary failure > library(ctest) > version _ platform Windows arch x86 os Win32 system x86, Win32 status major 1 minor 0.0 year 2000 month

...don't care to understand anything technical with FC-RHEL development and focus, and just get things dead wrong. Especially things that have redistribution and/or licensing issues, or the fact that sooner or later, newer versions have to be adopted. In fact, many people seem to be "wishy washy" on whether Red Hat should "hold back/backport" or "adopt newer" releases. The reality is that Red Hat doesn't ship anything in RHEL that hasn't been through Fedora Core prior (with rare exception, like MySQL 4 in RHEL4 that wasn't in FC2/FC3 -- kinda shocked e...

...h -mfma -ffast-math, this generates fma(x, y, x). Even >>>> though this transform superficially appears to use distributivity, >>>> that’s somewhat debatable because the fma computes the whole result >>>> without any intermediate rounding, so it’s pretty wishy-washy to say >>>> that it’s been used here. >>> >>> It most definitely has been used here, because of inf/nan behavior. >>> >>> inf*(0 + 1) == inf >>> inf*0 + inf == nan >>> >>> (I actually fixed this bug in the past because it o...

Hello all, Would packages using the underscore placeholder with the native pipe need to also depend on R >= 4.2.0? There appear to be a number, modifying Ivan's GitHub search: https://github.com/search?q=org%3Acran+path%3A%2F%5B.%5D%5BRr%5Dd%3F%24%2F+%2F%5Cs%5C%7C%3E%5Cs.*%3D%5Cs%3F_%2F&type=code Regards, Ian ____ Ian Farm Laboratory Manager, The Agroecology Lab University of Maine

hi folks, in my (unlucky) first test of ogg vs other encoders, i found a case where wma and mp3pro sound much better than ogg at 64k. can anyone suggest a setting that i haven't tried yet that can rival the wma and mp3pro samples at 64k? it's the "gravel effect" that is troublesome. the part in question is the first 15 seconds of this wave file:

I''m working on writing features for a wizard. The wizard collects information from a number of different forms, and you can navigate through it in a number of ways. Anyhow one of these forms is a customer form collecting name, and email. In the context of the wizard I feel that the following scenarios Scenario: Given I step to customer And I fill in my customer details

Dear R users, I have noticed that my R startup is extremely slow. It takes almost 3 minutes from "double-click" to R prompt. I have been running R-0.64.1 till recently and it took about 30 sec. I still have access to R-0.64.1. When I started it up, it took about 25 sec. Can anyone tell me if this is a bug in R or a problem with my machine? Note: This is after bootup with R being the

Where are we going? It's time to start thinking ahead and really figure out how to make Compiz survive, specially in lieu of Dennis' suggestion. The reality is that there has been the equivalent of no progress since the merge. We've basically only been in maintenance mode. The reason for this, from my point of view, is a complete lack of direction and leadership. We've