BioC++ core-0.7.0
The Modern C++ libraries for Bioinformatics.
 
Loading...
Searching...
No Matches
List of all members
bio::ranges::views::deep< underlying_adaptor_t > Class Template Reference
Ranges » Views

A wrapper type around an existing view adaptor that enables "deep view" behaviour for that view. More...

#include <bio/ranges/views/deep.hpp>

+ Inheritance diagram for bio::ranges::views::deep< underlying_adaptor_t >:

Public Member Functions

Constructors, destructor and assignment
constexpr deep () noexcept=default
 Defaulted.
 
constexpr deep (deep const &) noexcept=default
 Defaulted.
 
constexpr deep (deep &&) noexcept=default
 Defaulted.
 
constexpr deep & operator= (deep const &) noexcept=default
 Defaulted.
 
constexpr deep & operator= (deep &&) noexcept=default
 Defaulted.
 
 ~deep () noexcept=default
 Defaulted.
 

Related Functions

(Note that these are not member functions.)

Template argument deduction guides.
template<typename underlying_adaptor_t >
 deep (underlying_adaptor_t &&inner) -> deep< underlying_adaptor_t >
 Template argument deduction helper that preserves lvalue references and turns rvalue references into values.
 

Detailed Description

template<typename underlying_adaptor_t>
class bio::ranges::views::deep< underlying_adaptor_t >

A wrapper type around an existing view adaptor that enables "deep view" behaviour for that view.

Template Parameters
underlying_adaptor_tThe type of the adaptor being wrapped.

Deep views

If you pass a range to a view that view performs some transformation on that range. If the range passed is multi-dimensional (i.e. a range-of-ranges) that transformation happens on the outermost range. So if you call std::views::reverse on a range-of-dna-ranges, it will revert the order of the dna-ranges, but leave the dna-ranges themselves unchanged.

In some cases this is not desirable or even possible, i.e. bio::views::complement performs it's operation on nucleotide-ranges and it would be logical to do so, even it is passed a range-of-nucleotide-ranges (it obviously cannot transform the outer range). We call these views "deep views" as they always perform their operation on the innermost ranges of a multi-dimensional range; in case the input is a one-dimensional range, deepness does not modify the behaviour.

Using views::deep

Strictly speaking, bio::views::deep is a view adaptor adaptor, i.e. it gets passed another adaptor when being constructed (not via the pipe!) and returns an adaptor that behaves like the underlying one, except being deep.

You can use it mostly like any other view (adaptor) with some subtle differences, illustrated in the examples below.

View properties

The returned view has the same requirements and guarantees as those of the underlying adaptor type, except that it is also deep, i.e. if the underlying range is range-of-ranges, all transformations apply to the innermost ranges and conversely the requirements also apply to the innermost ranges of the underlying range and guarantees apply to the innermost ranges of the returned range.

For the higher dimensions (all except the innermost ranges) the following properties hold:

Concepts and traits urng_t (underlying range type) rrng_t (returned range type)
std::ranges::input_range required preserved
std::ranges::forward_range preserved
std::ranges::bidirectional_range preserved
std::ranges::random_access_range preserved
std::ranges::contiguous_range lost
std::ranges::viewable_range required guaranteed
std::ranges::view guaranteed
std::ranges::sized_range preserved
std::ranges::common_range preserved
std::ranges::output_range lost
bio::ranges::const_iterable_range preserved
std::ranges::range_reference_t std::ranges::input_range std::ranges::input_range + std::ranges::view

Examples

Wrapping an adaptor that takes no parameters ("range adaptor <i>closure</i> object"):

#include <vector>
#include <bio/alphabet/nucleotide/dna5.hpp>
#include <bio/ranges/views/deep.hpp>
#include <ranges>
namespace my
{
// You can create a permanent alias:
inline auto const deep_reverse = bio::views::deep{std::views::reverse};
}
int main()
{
using namespace bio::alphabet::literals;
std::vector<std::vector<bio::alphabet::dna5>> foo{"AAATTT"_dna5, "CCCGGG"_dna5};
auto r = foo | std::views::reverse; // == [ [C,C,C,G,G,G], [A,A,A,T,T,T] ]
// These two are equivalent:
auto e = foo | my::deep_reverse; // == [ [T,T,T,A,A,A], [G,G,G,C,C,C] ]
auto d = foo | bio::views::deep{std::views::reverse}; // == [ [T,T,T,A,A,A], [G,G,G,C,C,C] ]
}
deep.hpp
Provides bio::views::deep.
dna5.hpp
Provides bio::alphabet::dna5, container aliases and string literals.
bio::alphabet::literals
An inline namespace for alphabet literals. It exists to safely allow using namespace.
Definition: aa10li.hpp:183

Wrapping an adaptor that takes parameters:

#include <vector>
#include <bio/alphabet/nucleotide/dna5.hpp>
#include <bio/ranges/views/deep.hpp>
#include <bio/ranges/views/take.hpp>
namespace my
{
inline auto const deep_take = bio::views::deep{std::views::take};
}
int main()
{
using namespace bio::alphabet::literals;
std::vector<std::vector<bio::alphabet::dna5>> foo{"AAATTT"_dna5, "CCCGGG"_dna5};
auto t = foo | std::views::take(1); // == [ [A,A,A,T,T,T] ]
auto d = foo | bio::views::deep{std::views::take}(1); // == [ [A], [C] ]
// constructor arguments passed via {} and arguments to underlying view passed via ()
// In this case especially, an alias improves readability:
auto e = foo | my::deep_take(1); // == [ [A], [C] ]
}
take.hpp
Provides bio::views::take.

The above example illustrates that views::deep has two sets of arguments, the arguments to construct this adaptor, and the arguments passed to the underlying adaptor when calling this adaptor. You can use () for both, but we highly recommend to use {} to not confuse these; or just use an alias.

Attention
Note that in the case of parameter handling the arguments to views::deep are copied to each invocation of the underlying adaptor if they are temporaries. This is no problem for small objects like the integer above, but might be expensive for larger ones. To avoid this, pass in references to external objects instead of temporaries:
#include <vector>
#include <bio/alphabet/nucleotide/dna5.hpp>
#include <bio/ranges/views/deep.hpp>
#include <bio/ranges/views/take.hpp>
namespace my
{
inline auto const deep_take = bio::views::deep{std::views::take};
}
int main()
{
using namespace bio::alphabet::literals;
std::vector<std::vector<bio::alphabet::dna5>> foo{"AAATTT"_dna5, "CCCGGG"_dna5};
int i = 3;
auto f = foo | my::deep_take(i); // takes `i` as a reference!
}

Wrapping an adaptor including its arguments:

#include <vector>
#include <bio/alphabet/nucleotide/dna5.hpp>
#include <bio/ranges/views/deep.hpp>
#include <ranges>
namespace my
{
inline auto const deep_take1 = bio::views::deep{std::views::take(1)};
}
int main()
{
using namespace bio::alphabet::literals;
std::vector<std::vector<bio::alphabet::dna5>> foo{"AAATTT"_dna5, "CCCGGG"_dna5};
auto t = foo | std::views::take(1); // == [ [A,A,A,T,T,T] ]
auto d = foo | bio::views::deep{std::views::take(1)}; // == [ [A], [C] ]
// constructor arguments passed via {} and arguments to underlying view hardcoded inside
// or with an alias defined previously
auto e = foo | my::deep_take1; // == [ [A], [C] ]
}

In the above example the argument to the underlying adaptor is hardcoded and can't be changed at the call-site. It is less flexible, but does not require workarounds for arguments that are expensive (or impossible) to copy.

The documentation for this class was generated from the following file: