Erik Hollensbe
Erik Hollensbe
How would that work? On Sun, Feb 12, 2017 at 11:42 AM, Mike Gaffney wrote: > If not it'd be nice to have this as well. > > — >...
Sorry to be blunt; that seems really fragile. What's the use-case? On Sun, Feb 12, 2017 at 12:57 PM, Mike Gaffney wrote: > Was thinking it'd take an interface{} and...
Please look at the Value.String methods. they call inspect for the ugly cases, which is probably what Encode would do too. I don't know if I have a say in...
If you feel it's necessary enough for your application, would you be willing to submit a patch that we could discuss? On Sun, Feb 12, 2017 at 2:30 PM, Erik...
Agree with the collection methods, but I think personally that string coercion should be left up to the user. Just offering my opinion. Would you be willing to patch in...
while I was trying to verify this, I ran into a full panic with the following ruby: ``` ruby def foo end ``` The return value is indeed the `foo`...
makes sense. I'll see what I can do this week. On 6 Oct 2016, at 6:53, Mike Simons wrote: > @erikh I've replicated it but given that this code already...
Maybe this seems like a dumb idea and I hope it's ok if I jump in, but what's the reason that the name couldn't be made first-class? On Wed, Mar...
Maybe just some data in json files, parse and check the fields? Is that what you were thinking? I might be able to do this over an evening or weekend...
I'll put a reminder in to research over the weekend what needs to be done and hopefully get back to you then with more information. On Thu, Apr 13, 2017...