search for: imperatively

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

This adds imperative list manipulation functions inspired by Perl. The functions are passed list refs which get updated in place. This allows us to replace some awkward pure functional code like: let xs = ys in let xs = if foo then xs @ zs else xs in with: let xs = ref ys in if foo then append xs zs; --- mllib/common_utils.ml | 20 ++++++++++++++++++++ mllib/common_utils.mli | 36

On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > This adds imperative list manipulation functions inspired by Perl. > The functions are passed list refs which get updated in place. > > This allows us to replace some awkward pure functional code like: > > let xs = ys in > let xs = if foo then xs @ zs else xs in > > with: > > let xs = ref ys in

On Thu, Jul 07, 2016 at 06:08:43PM +0100, Richard W.M. Jones wrote: > On Thu, Jul 07, 2016 at 07:00:46PM +0200, Pino Toscano wrote: > > On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > > > This adds imperative list manipulation functions inspired by Perl. > > > The functions are passed list refs which get updated in place. > > > > > > This

Hey all, I just found Bryan Helmkamp''s (of webrat fame) slides on a presentation he did at GoRuCo 2008: http://www.brynary.com/2008/4/26/story-driven-development-slides-posted On slides 21-24 he talks about writing good stories and shows gives two examples.. the way not to do it and the way to do it. You can also see the video of the presentation at confreaks

On Thu, Jul 07, 2016 at 07:00:46PM +0200, Pino Toscano wrote: > On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > > This adds imperative list manipulation functions inspired by Perl. > > The functions are passed list refs which get updated in place. > > > > This allows us to replace some awkward pure functional code like: > > > > let xs = ys

On Fri, Jul 08, 2016 at 09:10:51AM +0100, Richard W.M. Jones wrote: > On Thu, Jul 07, 2016 at 06:08:43PM +0100, Richard W.M. Jones wrote: > > On Thu, Jul 07, 2016 at 07:00:46PM +0200, Pino Toscano wrote: > > > On Thursday 07 July 2016 17:30:03 Richard W.M. Jones wrote: > > > > This adds imperative list manipulation functions inspired by Perl. > > > > The

Dear R community, I have one function, it works for small data set, but does not work on large data set, can anyone help me with this? > #creat new variable by dividing each aa dimer by total_length. > imper<-function(x, file) { + round(x/file$length, 5) + } > dim(test) [1] 999 2402 > test[varname[2:2401]]<-

The coding guidelines say: > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). This means that functions that just compute or access a value (no side-effects) should be named e.g. `getParent()`, rather than `parent()` as they are in

Forgive the long post, just looking for input/advice/alternate opinions.. Like many I think that going through the exercise of framing user requests in Cucumber terms(Features, Scenarios..) really helps facilitate necessary conversations and avoid time wasted implementing the wrong thing(e.g. as a requirement/specification tool). However, I''m a bit confused when it comes to

No functional change in this commit. --- builder/downloader.ml | 40 +++++++++++++++++++--------------------- v2v/copy_to_local.ml | 26 +++++++++++--------------- v2v/vCenter.ml | 34 ++++++++++++++++------------------ 3 files changed, 46 insertions(+), 54 deletions(-) diff --git a/builder/downloader.ml b/builder/downloader.ml index 3c9ba18..2a3f76f 100644 --- a/builder/downloader.ml

On Fri, 4 Oct 2019 at 18:11, Japheth Cleaver <cleaver at terabithia.org> wrote: > > On 10/4/2019 8:17 AM, Lamar Owen wrote: > > On 10/4/19 10:40 AM, Valeri Galtsev wrote: > >> My impression is younger generation doesn't value rules that > >> programmers were following 2-3 decades ago. One of which is: > >> > >> Do not make any changes [in

> On 24 May 2018, at 20:19, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The coding guidelines say: > > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). > > This means that functions that

On 24.05.2018 13:11, Dean Michael Berris via llvm-dev wrote: > >> On 24 May 2018, at 20:19, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> The coding guidelines say: >>> Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case

Hi, I'm trying to emit FP_ROUND f64 -> f32 considering a mips target that only supports single float point operations. The problem is that f32 is considered legal on this target but f64 doesn't and the only way I can codegen this instruction is using setConvertAction(MVT::f64, MVT::f32, Expand), which issues a EmitStackConvert. What if I want a libcall instead? What should I do? The

Hi all, I am trying to compile a high-level imperative OOP-like language to the LLVM IR. Do we have any "generic" way of translating a non-SSA form to the LLVM IR's SSA? There are lots of LLVM front-ends now. Do they do such translation individually? or there is some common non-SSA IR that we can translate to, and can be converted to the LLVM IR automatically? I did not find such

So the right way to do it -- it seemed to work when I tried it, at least -- is metaflac --remove-all --dont-use-padding filename.flac ? I guess that these features make it more imperative than ever to watch the timestamps and not to validate a FLAC with an MD5 that is older than the FLAC is.

I just discovered something awful. The EventLog#tail method does not work the way I thought it did. Instead of picking up new events as they''re added, it''s really just iterating backwards through the current event log backwards. Look at this sample below. The first record is correct. Then another event happens, but instead of the latest record, I get an *earlier*

Basic support for Small bss and data. The rest is implemented with target specific logic and will be commited as soon as it's ok to commit this patch. -- Bruno Cardoso Lopes http://www.brunocardoso.cc "When faced with untenable alternatives, you should consider your imperative." -------------- next part -------------- A non-text attachment was scrubbed... Name: smallsections.patch

On Tue, Feb 6, 2018 at 2:56 PM David Woodhouse <dwmw2 at infradead.org> wrote: > On Tue, 2018-02-06 at 22:08 +0000, Chandler Carruth wrote: > > So, I was waiting to hear a definitive response on whether using aliases > is hard, and didn't see one here, which is why I haven't responded further. > > However, a colleauge pointed me at an LKML thread where it seems