Skip to content
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.

Sign up for GitHub

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

Jump to bottom

metal: Migrate to objc2 architecture with objc2-metal bindings #225

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

metal: Migrate to objc2 architecture with objc2-metal bindings #225

wants to merge 2 commits into from

Commits on Jul 4, 2024

  1. metal: Migrate to objc2 architecture with objc2-metal bindings 

    The current `objc` crate stack is completely unmaintained and has
severely fallen out of date with no updates for over 4 years.  The
`metal-rs` crate, built on top of this architecture, is completely
written by hand which is tedious to keep up-to-date, not to mention
has inconsistencies in its implementation.

All of this is superseded by the new `objc2` crate stack built by
@madsmtm.  Beyond providing what seems like a better, safer abstraction
over Objective-C, _all_ bindings are completely autogenerated meaning
we'll no longer lag behind upstream bindings (requiring painstaking
manual patching) or have inconsistencies in the implementations, as long
as the generator is properly able to represent the bindings.
    @MarijnS95
    MarijnS95 committed Jul 4, 2024
    Configuration menu
    Copy the full SHA
    fa0b9ae View commit details
    Browse the repository at this point in the history

  2. Use target_vendor = "apple" instead of many custom target_oses

    @MarijnS95
    MarijnS95 committed Jul 4, 2024
    Configuration menu
    Copy the full SHA
    c16d45e View commit details
    Browse the repository at this point in the history