rust-windowing / raw-window-metal Goto Github PK

Supporting multiple version would be nice of course but currently I can't estimate the overhead for this as I haven't been following the rwh api changes lately tbh

Supporting multiple versions on the producer end is really easy via just implementing the traits for each version of the crate (feature-gated so that you don't have to have duplicate raw-window-handle dependencies). However, doing this for the consumer end (here and in ash-window for example) is more problematic as we should essentially have multiple versioned functions of metal_layer_from_handle() for each version of raw-window-handle, Alternatively we could implement a conversion trait for every version of raw-window-handle.

@notgull suggestions (preferably in a separate issue/PR/discussion)?

Originally posted by @MarijnS95 in #10 (comment)

In the Layer::Allocated case we should release the allocated layer to avoid leaking.
This could be done by implementing Drop and calling msg_send![layer, release].

@msiglreith seems to not have the time to maintain this any more (if I understood correctly?), so we should transfer this to the @rust-windowing organization. This was agreed on at the previous Winit meeting.

Tasks:

• Move repository.
• Transfer crate ownership on crates.io to madsmtm, daxpedda and kchibisov.
• Create a team @rust-windowing/raw-window-metal, and add that as publisher on crates.io.

Hi, it looks like both core-graphics and cocoa are out of date, would you mind updating them to their latest versions and publishing a new version of this crate?

• Update raw-window-handle dep to 0.5.0.
• API changes (function removed, signature changes)
• minor path release #10
• #8 (comment)