Modify

Ticket #7926 (closed Bugs: fixed)

Opened 15 months ago

Last modified 15 months ago

[Range] missing prototypes with predicate in lower_bound and upper_bound algorithm docs

Reported by: Kinugasa Tomonobu<kinugasa.tomonobu@…> Owned by: neilgroves
Milestone: To Be Determined Component: range
Version: Boost 1.52.0 Severity: Problem
Keywords: Cc:

Description

http://www.boost.org/doc/libs/1_52_0/libs/range/doc/html/range/reference/algorithms/non_mutating/lower_bound.html http://www.boost.org/doc/libs/1_52_0/libs/range/doc/html/range/reference/algorithms/non_mutating/upper_bound.html

missing prototypes with predicate version in lower_bound and upper_bound documents.

should add such as:

  • lower_bound
    template<
        class ForwardRange,
        class Value,
        class SortPredicate
        >
    typename range_iterator<const ForwardRange>::type
    lower_bound(ForwardRange& rng, Value val, SortPredicate pred);
    
    template<
        range_return_value re,
        class ForwardRange,
        class Value,
        class SortPredicate
        >
    typename range_return<const ForwardRange,re>::type
    lower_bound(ForwardRange& rng, Value val, SortPredicate pred);
    
  • upper_bound
    template<
        class ForwardRange,
        class Value,
        class SortPredicate
        >
    typename range_iterator<const ForwardRange>::type
    upper_bound(ForwardRange& rng, Value val, SortPredicate pred);
    
    template<
        range_return_value re,
        class ForwardRange,
        class Value,
        class SortPredicate
        >
    typename range_return<const ForwardRange,re>::type
    upper_bound(ForwardRange& rng, Value val, SortPredicate pred);
    

Attachments

Change History

comment:1 Changed 15 months ago by nathanridge

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

(In [82621]) [range] fixed #7926 (missing prototypes for lower_bound and upper_bound in docs)

comment:2 Changed 15 months ago by nathanridge

(In [82622]) [range] merge documentation fix from trunk (refs #7926)

comment:3 Changed 15 months ago by nathanridge

Fixed for 1.53 - thanks!

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.