Expose object_safe property on type Trait

[obi1kenobi]

Rustdoc as of format version 28 shows whether traits are object-safe or not: https://docs.rs/rustdoc-types/latest/rustdoc_types/struct.Trait.html#structfield.is_object_safe

We want to expose a new object_safe: Boolean! field on type Trait so we can query this information in cargo-semver-checks lints.

[devanbenz]

@obi1kenobi This is WeblWabl from the timclicks discord - we had a brief discussion about OSS contribs :D I think I'm going to take on this issue & obi1kenobi/cargo-semver-checks#635 since they are dependencies.

[obi1kenobi]

Nice! Look at how type Trait implements its unsafe property, you can use its implementation as a guide since it should be quite analogous.

[devanbenz]

@obi1kenobi Can I get permission to push to the github repository? I don't think I have read rights 🤔

[obi1kenobi]

Could you try forking the repo and opening a PR that way? The publishing config is a bit sensitive here so I'd rather not mess with the permissions if it's possible to avoid it right now.

…

On Fri, Feb 9, 2024, 10:19 PM WeblWabl ***@***.***> wrote: @obi1kenobi <https://github.com/obi1kenobi> Can I get permission to push to the github repository? I don't think I have read rights 🤔 — Reply to this email directly, view it on GitHub <#320 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR5MSQEQRFEPM5S4M6UYILYS3RNDAVCNFSM6AAAAABBZCT2VGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHAZTKMZTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[devanbenz]

We could probably link this commit to the issue and close it out now :D #323

[obi1kenobi]

Nice! Resolved in #323 and published in v28.0.2.