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

Release 0.2.0 #13

Open
nirvdrum opened this issue Mar 21, 2017 · 5 comments
Open

Release 0.2.0 #13

nirvdrum opened this issue Mar 21, 2017 · 5 comments

Comments

@nirvdrum
Copy link
Contributor

nirvdrum commented Mar 21, 2017

It looks like the 0.2.0 release won't require building the extension at all if String.method_defined?(:unicode_normalize) is true. This is a really nice benefit on modern Ruby versions. Is there anything holding up promoting the beta to a proper release?

@nirvdrum nirvdrum changed the title Release 0.2 Release 0.2.0 Mar 21, 2017
@nomoon
Copy link

nomoon commented Jul 13, 2017

I really hope there's still a way to ensure that unf_ext can be enabled despite String.unicode_normalize being available. Ruby's built-in Unicode normalization is abysmally slow (>10x slower than unf), and unf is among the fastest available on any platform. Ever since unf was recently updated to support Unicode 9.0 (and unf_ext has followed), there should be feature parity between both implementations.

@bastelfreak
Copy link

ping @knu. Or maybe even release a 1.0.0 version? This since is around for ages it really looks stable.

@anatol
Copy link

anatol commented Jan 27, 2020

Please release 0.2.0 to stable. A lot of libraries need it.

@anatol
Copy link

anatol commented Jun 5, 2020

Hi @knu any word on the new release?

@majioa
Copy link

majioa commented Dec 19, 2022

1.0.0 will be better. @knu ?

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

5 participants