dmlap/shtml — comment on commit 01c5a7c0c22d07e7bfc7e9eee26f982c0f823910
File: src/test/scala/HtmlInterpreterSpecs.scala line 12
By dmlap:

Actually, that bit of crazy was because I originally wrote that on a plane and didn't have the specs documentation available. I'd like to replace all of the must_==s with more expressive marchers (if I ever get the chance). I'd love your opinion on the API once I get the "selector snippets" in there-- I think it should be usable but I've been known to be waaaaayyyy wrong about that sort of thing :)

Sent from my iPhone

On Nov 30, 2011, at 9:52 AM, Daniel Spiewak wrote:

> :-) I sort of suspected Java immersion when I noticed the "true must_== …" syntax. That's backwards, you know. The error messages there will be weird. Also, it's an unnecessary practice in Scala, since == on null is special-cased to avoid NPEs.
>
> Daniel
>
> On Nov 30, 2011, at 6:42 AM, "David LaPalomento" wrote:
>
>> Wow, you're on the ball. I've been writing way too much Java recently, forgive me!
>>
>> David
>>
>> On Nov 30, 2011, at 1:04 AM, Daniel Spiewak wrote:
>>
>>> You do know that `implements` isn't really valid Scala, right? ;-)
>>>
>>> ---
>>> Reply to this email directly or view it on GitHub:
>>> https://github.com/dmlap/shtml/commit/01c5a7c0c22d07e7bfc7e9eee26f982c0f823910#commitcomment-756406
>>
>> ---
>> Reply to this email directly or view it on GitHub:
>> https://github.com/dmlap/shtml/commit/01c5a7c0c22d07e7bfc7e9eee26f982c0f823910#commitcomment-757227
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/dmlap/shtml/commit/01c5a7c0c22d07e7bfc7e9eee26f982c0f823910#commitcomment-757798