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

[Kinetic] Adding 'template' to resolve compile error #1685

Merged
merged 1 commit into from
Feb 10, 2020

Conversation

kunaltyagi
Copy link
Contributor

@kunaltyagi kunaltyagi commented Apr 3, 2019

This syntax has already been used a few lines above in the same file. It prevents the compiler from assuming that add is being compared to i using the operator <.

Hoping to see this land soon 😄 (or am I the only one using Kinetic now 😰 )

Checked melodic-devel, and this bug has been resolved there

@dirk-thomas dirk-thomas changed the title Adding 'template' to resolve compile error [Kinetic] Adding 'template' to resolve compile error Apr 3, 2019
@dirk-thomas
Copy link
Member

This is a backport of #1388.

or am I the only one using Kinetic now

I assume you are either using Fedora or a custom g++ version on Ubuntu.

Hoping to see this land soon

It will likely be a while since releasing a new version into Melodic is certainly higher on the priority list.

@kunaltyagi
Copy link
Contributor Author

It will likely be a while since releasing a new version into Melodic is certainly higher on the priority list.

No problem.

You mentioned correctly that this is a backport of #1388. I accidentally linked my fork instead of ros repo for the commit (corrected now). Is there a separate process for backports or does this suffice?

And yes, I'm using an upgraded gcc on Ubuntu. I was just quipping because Kinetic is quite old now (and not receiving updates on many packages, rightfully so) and hopefully other people have planned the move to Melodic. It's hard to convey tone via text.

Cheers 😃

@dirk-thomas
Copy link
Member

Is there a separate process for backports or does this suffice?

Usually all backports are being merged in a single PR which enumerates all changes and mentions if / why the are (not) backported, e.g. #1477.

This is fine as is.

@lucbettaieb
Copy link

@dirk-thomas Can this be merged please? Message filters is broken on kinetic without this.

@lucbettaieb
Copy link

@dirk-thomas @gerkey @mikepurvis ping ping <3

ebrand0007 pushed a commit to ebrand0007/ros_comm that referenced this pull request May 22, 2019
@dirk-thomas
Copy link
Member

Merging out-of-band since it is already part of a Melodic release and the original change won't be consider for backporting again.

@dirk-thomas dirk-thomas merged commit 53ab192 into ros:kinetic-devel Feb 10, 2020
@kunaltyagi kunaltyagi deleted the kinetic-devel branch February 11, 2020 03:03
@DLu DLu mentioned this pull request Jul 9, 2020
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

Successfully merging this pull request may close these issues.

3 participants