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.

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

Upgrade to rustc 1.0.0-dev (47551b574 2015-04-14) #62

Merged
merged 1 commit into from May 6, 2015
Merged

Conversation

@SimonSapin
Copy link
Member

SimonSapin commented May 6, 2015

No description provided.

@SimonSapin
Copy link
Member Author

SimonSapin commented May 6, 2015

I know nothing about Core Foundation, but this new from_i32 method looks close enough to the existing from_i64.

SimonSapin added a commit that referenced this pull request May 6, 2015
Upgrade to rustc 1.0.0-dev (47551b574 2015-04-14)
@SimonSapin SimonSapin merged commit c8236c2 into master May 6, 2015
@SimonSapin SimonSapin deleted the rustup_20150414 branch May 6, 2015
jdm pushed a commit that referenced this pull request Feb 1, 2018
Implemented NSTabView and NSTabViewItem. Simple example included. Again :)

Hi,

A long time ago I created PR #62, sadly life got in the way and I was unable fix the issues with the PR.

I've updated the code to the current codebase.

Hope this is useful for someone.
Thanks!

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/cocoa-rs/139)
<!-- Reviewable:end -->
jdm pushed a commit that referenced this pull request Feb 1, 2018
Add functions for controlling subpixel positioning

<!-- Reviewable:start -->
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/core-graphics-rs/62)
<!-- Reviewable:end -->
jdm pushed a commit that referenced this pull request Feb 1, 2018
Deal with two ultra-trivial warnings

I was too lazy to set git up and clone the repo locally, so these are the only warnings from the mondo list in #62 that I could do anything about right now. I'd like to get to at least some of the rest—the private-type-in-public-interface ones seem at first glance to be pretty doable, but I'd need to be able to run the compiler over the code to check for cascades.

(The fact I did this entirely in the Github UI also means I couldn't squash the two commits myself. Sorry.)

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/core-text-rs/64)
<!-- Reviewable:end -->
jdm pushed a commit that referenced this pull request Feb 1, 2018
Fix private-in-public warnings (error E0446)

Fix use of extern static warnings by wrapping in unsafe block (error E0133)

Fix zero-size struct warnings on certain CT* types
jdm pushed a commit that referenced this pull request Feb 1, 2018
Fix core-text related warnings (#62)

### Fix private-in-public warnings (error E0446)
Fixed by prepending `pub` to the offending types. Not sure if its the best way but it was the only thing that worked. Other methods I've tried to maintain privateness:
* Replace with an empty enum. That threw an error.
* Make it public and wrap within a private module. That threw an error too as `#[repr(C)]` does not accept modules

### Fix use of extern static warnings by wrapping in unsafe block (error E0133)
I think this is self-explanatory.

### Fix zero-size struct warnings on certain CT* types
Wrap around c_void as I believe the types are only used as pointers. Again, let me know if there is a better way to do this. I've tried following [this discussion](rust-lang/rust#27303) on opaque C types but I don't think there is a consensus. I came across this [discussion](Rust-SDL2/rust-sdl2#442) from the Rust SDL2 bindings and they eventually [opted](Rust-SDL2/rust-sdl2#445) for the solution that I implemented.

This is my first pull request (hence, first open source contribution) and I've been playing with Rust for the past few weeks. So please, if anything isnt up to standards or correctness, let me know! Also, to squash the other warnings, those changes would have to made in the modules where those types reside (core-graphics and core-foundation). I would gladly open a PR to fix those too if all looks good.

Thanks!

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/core-text-rs/65)
<!-- Reviewable:end -->
jdm pushed a commit that referenced this pull request Feb 1, 2018
jdm pushed a commit that referenced this pull request Feb 1, 2018
Bump foundation and graphics versions for #62.

This removes the last of the compiler warnings.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/core-text-rs/68)
<!-- Reviewable:end -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.