Charles Cooper
Charles Cooper
@0xETHengineer what is the purpose of this PR?
something like https://github.com/charles-cooper/elm-export/commit/d19502cdf885378919289eb00a59757c3ef431a0 this requires me to add a line ` , "import Exts.Date"` to my elm spec
make that https://github.com/charles-cooper/elm-export/commit/2a0259b89ed2e938f323b15cf7645cb0fb053445
i guess an issue that needs to be cleared up is that Elm's Date technically corresponds to Haskell's https://hackage.haskell.org/package/time-1.8.0.1/docs/Data-Time-LocalTime.html since it includes a non-timezoned time of day. the two paths...
> Would prefer that we create less language keywords so we can namespace better: > > ```vyper > from vyper.packaging import Bundle > IERC_X: Bundle = Bundle() # declare a...
I mean we could pick another name. But my point is it's not a keyword, you can still define variables and functions etc named `bundle`.
> I can create a function or state variable named `implements` too? yep
> So, these two don't conflict? > > ```vyper > # interface check > implements: ERC20 > > # state variable > implements: ERC20 > ``` aha yea they use...
closing this as superseded (for now) by https://github.com/vyperlang/vyper/pull/3786 and the spec could use some polishing, will revisit in 0.4.1
@erdewit I've been looking into this and I think the problem can be solved by protecting `_run_once` with leave/enter current task (probably here:) https://github.com/erdewit/nest_asyncio/blob/1ddc5509132a548ff4833e1a96ef6f8c3250cbeb/nest_asyncio.py#L117-L120 this is the approach i have...