Lokathor comments

Results 801 comments of


                                            Lokathor

Tracker: All unsafe blocks must be removed and then re-added one by one after careful verification of actual safety.

Every single FFI call must be left as unsafe unless you can demonstrate that it is safe. The default is that it's always unsafe. I'm not saying that you need...

Tracker: All unsafe blocks must be removed and then re-added one by one after careful verification of actual safety.

If we found a home for the crate with someone who actively uses Rust would you be interested in transferring ownership to an active Rust user?

Tracker: All unsafe blocks must be removed and then re-added one by one after careful verification of actual safety.

@HeroicKatora Well, from what I recall of ncurses (also haven't used it in a year or two) nearly every single function can segfault you if you didn't at least call...

Tracker: All unsafe blocks must be removed and then re-added one by one after careful verification of actual safety.

I agree that we should not hand the crate over to a total rando. More that I was looking to see if you'd be open to the idea at all....

Tracker: All unsafe blocks must be removed and then re-added one by one after careful verification of actual safety.

Until then, we've got a less argumentative title.

Tracking issue for Fn traits (`unboxed_closures` & `fn_traits` feature)

if by stack you mean heap, yes

Tracking issue for Fn traits (`unboxed_closures` & `fn_traits` feature)

Anyway, the fact that people can already make up their own trait based operator overloading, and even paper over the arity issue with a do_call! macro or whatever, means that...

Must a `const fn` behave exactly the same at runtime as at compile-time?

Note about option 2: changing the FP state causes LLVM UB with the standard IR operations. You have to use special IR ops that account for non-standard floating point state...

Must a `const fn` behave exactly the same at runtime as at compile-time?

I think they mean "have a trait impl that's const (and used in const contexts) and also the same impl as non-const (and used in non-const contexts)."