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

minor new release #29

Open
king-11 opened this issue Nov 4, 2024 · 5 comments
Open

minor new release #29

king-11 opened this issue Nov 4, 2024 · 5 comments

Comments

@king-11
Copy link

king-11 commented Nov 4, 2024

it has been 8 months since the last release the window-sys package change might be useful further upstream allowing users to fetch only one dependency so if it makes sense can we have a new release?

@soc
Copy link
Collaborator

soc commented Nov 4, 2024

Hi @king-11,

the window-sys package change might be useful further upstream allowing users to fetch only one dependency

which one?

Thanks,

Simon

@king-11
Copy link
Author

king-11 commented Nov 5, 2024

Most of the crates are using windows-sys 0.52 like tokio, request, tempfile, etc. so if dirs is used with them then it would pull in 0.48 for now without latest change.

@ScratchCat458
Copy link

In version 0.59.0 the HANDLE type alias has changed: [1] [2]

pub type HANDLE = *mut c_void; // 0.59.0 [1]
pub type HANDLE = isize; // 0.52.0 [2]

This is backwards incompatible with this line in lib.rs and is a fairly quick fix:

  let result = Shell::SHGetKnownFolderPath(
              &folder_id,
              0,
-             Win32::Foundation::HANDLE::default(),
+             std::ptr::null_mut(),
              &mut path_ptr
          );

Upgrading to support 0.59 would have to come at the cost of being unable to support the current version range (>= 0.48.0, < 0.53.0).

Worth keeping an eye on this regarding what the rest of the ecosystem is using, but unsure how we should proceed.

@king-11
Copy link
Author

king-11 commented Nov 5, 2024

Yeah I think there should be some version that supports a larger set of versions before proceeding onto a bump that would break backwards compatibility.

@king-11
Copy link
Author

king-11 commented Nov 14, 2024

@soc any thoughts how can be proceed to be in sync with the ecosystem referring the latest tokio Cargo.toml the max version is 0.52.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants