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

[EXPERIMENT] String- and number-specific bitwise ops #14459

Closed
p5pRT opened this issue Feb 1, 2015 · 6 comments

Comments

@p5pRT
Copy link

commented Feb 1, 2015

Migrated from rt.perl.org#123707 (status was 'resolved')

Searchable as RT123707$

@p5pRT

This comment has been minimized.

Copy link
Author

commented Feb 1, 2015

From @cpansprout

The new ops &. |. ^. ~. and the strictly-numeric behaviour of & | ^ ~ under the
‘bitwise’ feature are being added as an experiment in perl 5.22.0. This ticket
will collect bugs and other acceptance-criteria tickets to track before these
new ops can be considered accepted or failed in a future version of perl.

--

Father Chrysostomos

@p5pRT

This comment has been minimized.

Copy link
Author

commented Dec 17, 2017

From @cpansprout

On Sat, 31 Jan 2015 22​:07​:56 -0800, sprout wrote​:

The new ops &. |. ^. ~. and the strictly-numeric behaviour of & | ^ ~
under the
‘bitwise’ feature are being added as an experiment in perl 5.22.0.
This ticket
will collect bugs and other acceptance-criteria tickets to track
before these
new ops can be considered accepted or failed in a future version of
perl.

This feature has been in three stable releases of perl, with no changes to the implementation as far as I can remember. As evidenced by ticket #132589, this feature is actually being used in the wild, and the only bug report it has had is not actually a bug in Perl, but in a module.

I suggest we accept this feature as stable for 5.28, and enable it with ‘use v5.28‘.

--

Father Chrysostomos

@p5pRT

This comment has been minimized.

Copy link
Author

commented Dec 17, 2017

The RT System itself - Status changed from 'new' to 'open'

@p5pRT

This comment has been minimized.

Copy link
Author

commented Dec 18, 2017

From @xsawyerx

On Sun, 17 Dec 2017 11​:15​:03 -0800, sprout wrote​:

On Sat, 31 Jan 2015 22​:07​:56 -0800, sprout wrote​:

The new ops &. |. ^. ~. and the strictly-numeric behaviour of & | ^ ~
under the
‘bitwise’ feature are being added as an experiment in perl 5.22.0.
This ticket
will collect bugs and other acceptance-criteria tickets to track
before these
new ops can be considered accepted or failed in a future version of
perl.

This feature has been in three stable releases of perl, with no
changes to the implementation as far as I can remember. As evidenced
by ticket #132589, this feature is actually being used in the wild,
and the only bug report it has had is not actually a bug in Perl, but
in a module.

I suggest we accept this feature as stable for 5.28, and enable it
with ‘use v5.28‘.

Makes sense. Any objections?

@p5pRT

This comment has been minimized.

Copy link
Author

commented Jan 1, 2018

From @cpansprout

On Mon, 18 Dec 2017 07​:26​:49 -0800, xsawyerx@​cpan.org wrote​:

On Sun, 17 Dec 2017 11​:15​:03 -0800, sprout wrote​:

On Sat, 31 Jan 2015 22​:07​:56 -0800, sprout wrote​:

The new ops &. |. ^. ~. and the strictly-numeric behaviour of & | ^ ~
under the
‘bitwise’ feature are being added as an experiment in perl 5.22.0.
This ticket
will collect bugs and other acceptance-criteria tickets to track
before these
new ops can be considered accepted or failed in a future version of
perl.

This feature has been in three stable releases of perl, with no
changes to the implementation as far as I can remember. As evidenced
by ticket #132589, this feature is actually being used in the wild,
and the only bug report it has had is not actually a bug in Perl, but
in a module.

I suggest we accept this feature as stable for 5.28, and enable it
with ‘use v5.28‘.

Makes sense. Any objections?

There weren’t any, so I have gone ahead with this and merged by branch in commit b566b29.

--

Father Chrysostomos

@p5pRT

This comment has been minimized.

Copy link
Author

commented Jan 1, 2018

@cpansprout - Status changed from 'open' to 'resolved'

@p5pRT p5pRT closed this Jan 1, 2018
@p5pRT p5pRT added the Severity Low label Oct 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.