32d4c973e9
- Write sections on containers, algorithms, and runtime performance - Make sure examples consistently use 2 space tabs - Disable -Wunused-parameter for examples - Resolves #70 The requirement of pure functions is now documented. - Resolves #14 It turns out that the benefits of specifying the type of containers seems to be essentially limited to pattern matching. This is not enough to justify all the bad things it brings, especially considering the fact that recursion (currently the only use case for pattern matching) forces the creation of a new tuple at each step, which is disastrous. The unspecified-ness of the container's type is now documented.
42 lines
817 B
JSON
42 lines
817 B
JSON
<%
|
|
exec = (0..100).step(10).to_a
|
|
fusion = (0..50).step(10).to_a
|
|
%>
|
|
|
|
{
|
|
"title": {
|
|
"text": "Executable size for transform"
|
|
},
|
|
"yAxis": {
|
|
"title": {
|
|
"text": "Executable size (kb)"
|
|
},
|
|
"floor": 0
|
|
},
|
|
"tooltip": {
|
|
"valueSuffix": "kb"
|
|
},
|
|
"series": [
|
|
{
|
|
"name": "hana::tuple",
|
|
"data": <%= measure(:bloat, 'execute.hana.tuple.erb.cpp', exec) %>
|
|
}
|
|
|
|
, {
|
|
"name": "std::array",
|
|
"data": <%= measure(:bloat, 'execute.std.array.erb.cpp', exec) %>
|
|
}
|
|
|
|
, {
|
|
"name": "std::vector",
|
|
"data": <%= measure(:bloat, 'execute.std.vector.erb.cpp', exec) %>
|
|
}
|
|
|
|
<% if cmake_bool("@Boost_FOUND@") %>
|
|
, {
|
|
"name": "fusion::vector",
|
|
"data": <%= measure(:bloat, 'execute.fusion.vector.erb.cpp', fusion) %>
|
|
}
|
|
<% end %>
|
|
]
|
|
} |