Modify

Ticket #2355 (closed Bugs: fixed)

Opened 6 years ago

Last modified 4 years ago

discrepancy between std::accumulate and fusion::accumulate

Reported by: srajko Owned by: djowel
Milestone: Boost 1.42.0 Component: fusion
Version: Boost Development Trunk Severity: Cosmetic
Keywords: Cc: mr.chr.schmidt@…

Description

std::accumulate expects binary functions which take the accumulator as the first argument and the sequence element as the second argument. fusion::accumulate expects the arguments in reverse.

Attachments

fusion.diff.bz2 Download (41.2 KB) - added by cschmidt 5 years ago.
note: the actual patch exceeds the 256kb file size limit
proto.diff Download (1.8 KB) - added by cschmidt 5 years ago.

Change History

comment:1 Changed 5 years ago by cschmidt

  • Owner changed from djowel to cschmidt
  • Status changed from new to assigned

I am on it.

Changed 5 years ago by cschmidt

note: the actual patch exceeds the 256kb file size limit

Changed 5 years ago by cschmidt

comment:2 Changed 5 years ago by cschmidt

  • Status changed from assigned to new
  • Severity changed from Problem to Cosmetic
  • Cc mr.chr.schmidt@… added
  • Version changed from Boost 1.36.0 to Boost Development Trunk
  • Milestone changed from Boost 1.37.0 to Boost 1.42.0
  • Owner changed from cschmidt to djowel

comment:3 Changed 4 years ago by cschmidt

  • Status changed from new to closed
  • Resolution set to fixed

comment:4 Changed 4 years ago by ivg@…

I think, that in future, it will be good to list such backward-compatibility breaking API changes explicitly under a big fat heading "Incompatible changes". Boost is a modest library that is widly used. It's not in alpha realease. So API must remain stable.

comment:5 Changed 4 years ago by anonymous

+1

I just spent 2 hours unnecessary debugging after upgrading

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.