Kevin

We're running into occasional segfaults as well at seemingly the same spot. We can't reproduce, but it appears to happen once every 10,000+ `client.request(verb, uri, opts)` calls. I'm 99% sure...

I ran into something similar, and was able to work around it by disabling the `iframe.contentWindow` evasion: ```javascript const StealthPlugin = require('puppeteer-extra-plugin-stealth')(); StealthPlugin.enabledEvasions.delete('iframe.contentWindow'); puppeteer.use(StealthPlugin); ```

I'd also like to see this idea revived. Is there any way I can help?

We ran into this: ```ruby class A extend Literal::Attributes attribute :proc, Proc, :& end class B < A attribute :foobar, String end ``` ``` /Users/hangsu/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/literal-455f225574db/lib/literal/attributable.rb:68:in `module_eval': /Users/hangsu/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/literal-455f225574db/lib/literal/attributable.rb:71: syntax error, unexpected...

> Matthew reminded me that this could also be useful for regular apps for which DB connections are costly, e.g. Postgres without PGBouncer, etc. Particularly in job workers where it's...

@trevorturk We have an abstraction that creates and keeps track of our Fibers. Then we override `ActiveRecord::Base.connection` to raise if we ever call it inside a Fiber using `Fiber.current`. Something...

That focus list is perfect (maybe with the addition of `Literal::Decorator`). We were actually considering forking `literal` to accomplish exactly this. Let me know how we can help ❤️

> Some of the other stuff may never make it back in. I like the idea of `literal` being focused on type checking and related conveniences. If you wanted to...

We've never run into any problems with `attribute` at Clearscope, but that might be because we've never had the urge to mix `Literal::Attributes` with anything `ActiveRecord` or `ActiveModel`-related. I wouldn't...

I think we would need to consider block (`:&`), kwargs (`:**`) and rest (`:*`) as well. If anything, I would've expected `:positional` rather than `positional: true`