Looks like there will be Mojo also soon: https://www.modular.com/mojo
On Monday, June 5, 2023 at 10:48:20 AM UTC+2 Chary Chary wrote: > Martin, > > OK, thanks for the information! > > On Saturday, June 3, 2023 at 11:29:58 PM UTC+2 [email protected] wrote: > >> During my visit at PyCon recently it was impossible to miss the fact that >> a number of Python projects are rewriting their core in Rust for >> performance reasons. Rust and Python seem to be best friends. >> >> On Wed, May 31, 2023 at 4:02 AM Chary Chary <[email protected]> wrote: >> >>> Martin, >>> >>> re "With the Python community aiming in that direction it was >>> unavoidable I guess." >>> >>> Do I understand this correctly, that that there is a growing tendency to >>> write high speed extensions for python in rust rather than C/C++? >>> >>> On Tuesday, May 23, 2023 at 5:34:55 AM UTC+2 [email protected] wrote: >>> >>>> +Beancount >>>> >>>> Looks fun. I started toying around with Rust myself. >>>> With the Python community aiming in that direction it was unavoidable I >>>> guess. >>>> >>>> Plus the C++ protobuf story just isn't getting much better. >>>> I'm wondering if there's a nicer by-ref sharing story with protos and >>>> Rust, where an instance created in Rust can be shared to Python without >>>> making copies (and possibly mutated). >>>> I'd be curious to see if your parser can be made to produce protobufs. >>>> >>>> >>>> >>>> >>>> On Mon, May 22, 2023 at 9:51 AM Jonathan Cornaz <[email protected]> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I started a "big rewrite" of the beancount parser: beancount_parser_2 >>>>> <https://github.com/jcornaz/beancount_parser_2> >>>>> >>>>> It is now in alpha. Hopefully, I'll be able to stabilize it reasonably >>>>> quickly (but there's no ETA) >>>>> >>>>> This old implementation (beancount-parser) is now in "maintenance >>>>> mode". I'll still fix reported bugs, and I'll review/merge submitted pull >>>>> requests. But I won't actively implement new features on that version. >>>>> >>>>> The new implementation already has some features that the old one >>>>> hasn't: >>>>> >>>>> - line numbers of errors >>>>> - line numbers of directives >>>>> - more convenient to destructure the result because structs expose >>>>> public fields >>>>> - can treat the account as string slices >>>>> - can use any decimal type when parsing (f64, rust_decimal::Decimal, >>>>> and more) >>>>> - can catch more syntax errors (instead of silently ignoring >>>>> unknown syntax) >>>>> - single result type (instead of an iterator over results) >>>>> - and more... >>>>> >>>>> Though there are still many missing functionalities, you may want to >>>>> have a look at it ;-) >>>>> >>>>> — >>>>> Reply to this email directly, view it on GitHub >>>>> <https://github.com/jcornaz/beancount-parser/discussions/38>, or >>>>> unsubscribe >>>>> <https://github.com/notifications/unsubscribe-auth/AACSBE25P3LS3V464567Y5TXHNVN3ANCNFSM6AAAAAAYKPNV3Y> >>>>> . >>>>> You are receiving this because you are subscribed to this thread.Message >>>>> ID: <jcornaz/beancount-parser/repo-discussions/[email protected]> >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Beancount" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beancount/6e4eb19a-8de2-47c9-b57f-70b6c6f7b3adn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/beancount/6e4eb19a-8de2-47c9-b57f-70b6c6f7b3adn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/7860cefe-c44f-48d6-81f0-cfded7e6eb48n%40googlegroups.com.
