Francis George
Francis George
@gsinclair I agree with liking the existing really nice short syntax. Actually with the proposed change, you could still use that exact syntax, just the `include` statement would change slightly....
An example in my project is with my class Node. A node has x and y coordinates and a type (:corner, :curve etc). x and y must be Num and...
@alex-fedorov Polymorphism would be clean but I like the single entrypoint and it makes specifying paths as an array of arrays easier to convert. Pros and cons either way, but...
I think it's supposed to be as follows, with methods dynamically generated for the types named as values, so no symbols within the block. ``` ruby Contract(:a, :b) { [ArrayOf[a],...
Symmetry would be nice, but for implementation I can't think how it would work with Symbols, it would likely require changing every built in contract. Dynamic methods would work without...
@waterlink Hooray! I'm not surprised :)
Oh. From the simple work I did on `yard-contracts` I had to use Ripper which is what YARD uses for Ruby parsing, and it's a pile of junk. Ripper has...
Ah well good to hear the `parser` foundation is solid so far. It's an exciting idea, hopefully bringing some of the magic of Crystal's macros.
Same issue. But after multiple attempts of quitting game and wiggling the cartridge eventually I get it to start, but not sure if that's the repeated tries or the wiggling....
The issue is that `capybara-screnshot` decides what driver you're using based on what you call it, not what it actually is. Headless Chrome is just Selenium, so if you call...