Can't leak crate-private traits error in libcrux-ml-kem

[msprotz]

Can't leak crate-private traits error in libcrux-ml-kem

[msprotz]

I think the code got rewritten and I don't remember which set of revisions last triggered it. I'm ok with closing, and we'll reopen it if it resurfaces. Thanks.

[sonmarcho]

@Nadrieril I want to change the priority of this issue (make it P1) but it doesn't appear in the dashboard. Any idea where the issue comes from? (I had to add the issue by hand)

[Nadrieril]

Yeah it's a known limitation. GitHub project has an option to auto-import issues from one repo but only one. I chose aeneas a bit arbitrarily; this means we need to add charon issues to the project by hand. If we paid for a GitHub plan we'd have the option to auto-import from more repos. There might also be a way to use GitHub Actions to automate this, I'll have to look into it.

[Nadrieril]

@msprotz I think this is not due to charon itself but to the old rustc version it uses. The error says that it doesn't know the "private_bounds" lint, which was added to a more recent rustc version than the one we use. I think #186 should fix your issue.

[Nadrieril]

@msprotz Can you try with latest charon main?

[msprotz]

Yup I just need to wrap up my trait work first then will attempt upgrading tool versions. Expect a few days' delay.

[msprotz]

I can confirm this is fixed. Thanks!

Actually I just saw this again. Will try to send a repro soon.

[Nadrieril]

Has this happened again since?