-
-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update 2 syn #1557
Update 2 syn #1557
Conversation
This does not fix everything because some things were restructured.
We were expecting the parentheses, but now we do not get those. Instead, drop parens from our structs and parse directly.
This required several hours of hunting and is one of the consequences of the attribute layering change.
Considering only the inner args of the attribute is necessary in order to get the correct names so that we can emit correct SQL. Ideally we would have much more resilient parsing that could extract data out of a broader range of token streams passed in. However, that is not the case currently, so don't.
cc @NotGyro |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks largely mechanical, which is good. I’m sure it was a process tho!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the small error message issue and the comment I think this is good. Reading through Syn's changelog, there shouldn't be any silent breaking changes (i.e. if there's a breaking change that we haven't taken into account it won't let us compile) and this builds and passes tests on my machine so it looks like it should be all set. The most common edit I'm seeing here is the parse_terminated() change and that all looks correct.
As an aside, I'm glad Binding
got split into AssocType
and AssocConst
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eliminating 4 dependencies is nice, but we shouldn't pass up easy points on which to make the nightmarish code here more maintainable.
macro_rules! lazy_err { | ||
($span_expr:expr, $lit:literal $(, $tokens:tt),*) => { | ||
{ | ||
let spanning = $span_expr; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is so that the expr can resolve instead of being captured into the closure. This make the name lazy_err!
slightly confusing, perhaps, since this part is eagerly-evaluated, but a lot of exprs die instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed by adding docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me after the changes!
Per Syn's docs, the replacement of parse2()
with parse_args()
should be fine, since:
This is similar to pulling out the TokenStream from Meta::List and doing syn::parse2::(meta_list.tokens), except that using parse_args the error message has a more useful span when tokens is empty.
(quote from here )
Welcome to pgrx 0.12.0-alpha.1! Say the magic words with me! ```shell cargo install cargo-pgrx --locked --version 0.12.0-alpha.1 ``` # Breaking Changes ## No more dlopen! Perhaps the most exciting change this round is @usamoi's contribution in #1468 which means that we no longer perform a `dlopen` in order to generate the schema. The cost, such as it is, is that your pgrx extensions now require a `src/bin/pgrx_embed.rs`, which will be used to generate the schema. This has much less cross-platform issues and will enable supporting things like `cargo binstall` down the line. It may be a bit touchy on first-time setup for transitioning older repos. If necessary, you may have to directly add a `src/bin/pgrx_embed.rs` and add the following code (which should be the only code in the file, though you can add comments if you like?): ```rust ::pgrx::pgrx_embed!(); ``` Your Cargo.toml will also want to update its crate-type key for the library: ```toml [lib] crate-type = ["cdylib", "lib"] ``` ## Library Code - pgrx-pg-sys will now use `ManuallyDropUnion` thanks to @NotGyro in #1547 - VARHDRSZ `const`s are no longer `fn`, thanks to @workingjubilee in #1584 - We no longer have `Interval::is_finite` since #1594 - We translate more `*_tree_walker` functions to the same signature their `*_impl` version in Postgres 16 has: #1596 - Thanks to @eeeebbbbrrrr in #1591 we no longer have the `pg_sql_graph_magic!()` macro, which should help with more things in the future! # What's New We have quite a lot of useful additions to our API: - `SpiClient::prepare_mut` was added thanks to @XeniaLu in #1275 - @usamoi also contributed bindings subscripting code in #1562 - For `#[pg_test]`, you have been able to use `#[should_panic(expected = "string")]` to anticipate a panic that contains that string in that test. For various reasons, `#[pg_test(error = "string")]` is much the same. Now, you can also use `#[pg_test(expected = "string")]`, in the hopes that is easier to stumble across, as of #1570 ## `Result<composite_type!("..."), E>` support - In #1560 @NotGyro contributed support for using `Result<composite_type!("Name"), E>`, as a case that had not been handled before. ## Significantly expanded docs Thanks to @rjuju, @NotGyro, and @workingjubilee, we now have significantly expanded docs for cargo-pgrx and pgrx in general. Some of these are in the API docs on https://docs.rs or the READMEs, but there's also a guide, now! It's not currently published, but is available as an [mdbook](https://github.com/rust-lang/mdBook) in the repo. Some diagnostic information that is also arguably documentation, like comments and the suggestion to `cargo install`, have also been improved, thanks to @workingjubilee in - #1579 - #1573 ## `#[pg_cast]` An experimental macro for a `CREATE CAST` was contributed by @xwkuang5 in #1445! ## Legal Stuff Thanks to @the-kenny in #1490 and @workingjubilee in #1504, it was brought to our attention that some dependencies had unusual legal requirements. So we fixed this with CI! We now check our code included into pgrx-using binaries is MIT/Apache 2.0 licensed, as is common across crates.io, using `cargo deny`!. The build tools will have more flexible legal requirements (partly due to the use of Mozilla Public License code in rustls). # Internal Changes Many internal cleanups were done thanks to - @workingjubilee in too many PRs to count! - @thomcc found a needless condition in #1501 - @nyurik in too many PRs to count! In particular: - we now actually `pfree` our `Array`s we detoasted as-of #1571 - creating a `RawArray` is now low-overhead due to #1587 ## Soundness Fixes We had a number of soundness issues uncovered or have added more tests to catch them. - Bounds-checking debug assertions for array access by @NotGyro in #1514 - Fix unsound `&` and `&mut` in `fcinfo.rs` by @workingjubilee in #1595 ## Less Deps Part of the cleanup by @workingjubilee was reducing the number of deps we compile: * cargo-pgrx: reduce trivial dep usages in #1499 * Update 2 syn in #1557 Hopefully it will reduce compile time and disk usage! ## New Contributors * @the-kenny made their first contribution in #1490 * @xwkuang5 made their first contribution in #1445 * @rjuju made their first contribution in #1516 * @nyurik made their first contribution in #1533 * @NotGyro made their first contribution in #1514 * @XeniaLu made their first contribution in #1275 **Full Changelog**: v0.12.0-alpha.0...v0.12.0-alpha.1
We have not been receiving updates to syn for a while, because we are on syn 1 still. Update to syn 2 and lift it into the workspace, which requires revamping how several
proc_macro_attribute
s are parsed. In the process, sprinkle pgrx-sql-entity-graph with paranoid amounts oftrack_caller
, expects, and compound errors on the unhappy path, to try to make the code start producing useful error spans.Then also drop unused features from some of our dependencies to completely erase syn 1 from the dependency tree. We don't meddle with any compressible sections, because we just look at exported symbols, not debuginfo, so I believe this is inconsequential. It's acceptable to revert that part of this change, however, if it doesn't actually work out.
Removes 4 crates from the dependency tree
The syn changes include:
syn::LifetimeDef
is nowLifetimeParam
syn::ImplItem::Method
is nowsyn::ImplItem::Fn
syn::ImplItemMethod
is nowsyn::ImplItemFn
syn::Expr::Type
no longer existsyn::MetaNameValue
replaces itslit
field withvalue
, as it accepts non-literalssyn::GenericArgument::Binding
is nowGenericArgument::AssocType
syn::Attribute
hid itspath
field as.path()
syn::Attribute
hid itstoken
field, so there is onlyToTokens
syn::Attribute
changed how it structures access to its args. We now parse inner args of asyn::Attribute
for our proc-macro attributes like#[pg_operator]
, without considering parentheses.