search for: not_null

I have to say `not_null(v)` reads more like an assertion than a predicate, in which case `isa<T>(not_null(v))` reads like it has the exact same semantics that `isa<T>(v)` has currently—asserts that `v` is not null. I don't dispute that you can *make* it have the desired semantics, it just won't *look*...

...a T or nullptr", which does not match the implementation semantics "v is a T and not null". On Sat, Apr 6, 2019 at 9:31 PM Zachary Turner <zturner at google.com> wrote: > Sorry, brain isn't fully working. I meant to call the function / type > `or_null` instead of `not_null` > > On Sat, Apr 6, 2019 at 11:16 AM Zachary Turner <zturner at google.com> wrote: > >> What about a type not_null_impl<T> and we could write: >> >> then you could just write bool x = isa<T>(not_null(val)); >> >> We provide a function not_nul...

What about a type not_null_impl<T> and we could write: then you could just write bool x = isa<T>(not_null(val)); We provide a function not_null<T> that returns a not_null_impl<T>: template<typename T> not_null_impl<T> not_null(T *t) { return not_null_impl<T>{t}; } and a specializ...

On Thu, Apr 4, 2019 at 12:58 PM Chris Lattner <clattner at nondot.org> wrote: > > > > > On Apr 4, 2019, at 5:37 AM, Don Hinton via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > I'd like to propose adding `isa_or_null<>` to replace the following usage pattern that's relatively common in conditionals: > > > > var &&

I am currently writing a search method for my rails applications and at the moment it works fine. I have the following in my game.rb: def self.search(search) if search find(:all, :conditions => [''game_name LIKE ? OR genre LIKE ? OR console LIKE ?'', "%#{search}%", "#{search}", "#{search}"]) else find(:all) end end No that searches