| std::make_integer_seq should provide O(logN) order | Bolero MURAKAMI | 27.01.13 04:42 |
|
| Re: std::make_integer_seq should provide O(logN) order | Nicol Bolas | 27.01.13 13:33 | What exactly is make_integer_seq from? What proposal is this about? |
| Re: [std-proposals] Re: std::make_integer_seq should provide O(logN) order | Daniel Krügler | 27.01.13 14:02 | 2013/1/27 Nicol Bolas <jmck...@gmail.com>:
> What exactly is make_integer_seq from? What proposal is this about?See: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3493.html I agree with Bolero that a logarithmic guarantee would be preferable. This would be the first example of such a guarantee, but it seems reasonable to have that. - Daniel |
| Re: [std-proposals] Re: std::make_integer_seq should provide O(logN) order | Jonathan Wakely | 12.03.13 06:23 | Yes, my reference implementation is O(N) but it's been pointed out to me that it should be O(logN). I'm not planning on a new revision of the paper before the next meeting, but was already planning on mentioning that the depth of instantiation can be reduced. |
| Re: [std-proposals] Re: std::make_integer_seq should provide O(logN) order | R. Martinho Fernandes | 12.03.13 06:27 | On Tue, Mar 12, 2013 at 2:23 PM, Jonathan Wakely <c...@kayari.org> wrote:If we're requiring a guarantee on this, why not go for something that user code cannot actually achieve? Why not require O(1) instantiations instead? Mit freundlichen Grüßen, Martinho |
| Re: [std-proposals] Re: std::make_integer_seq should provide O(logN) order | Jonathan Wakely | 12.03.13 06:33 |
Because the idea of the proposal is to standardise existing practice and I hoped it would be uncontroversial. The more bells and whistles are added to it the less likely it is to be accepted before the heat death of the universe. |
| Re: [std-proposals] Re: std::make_integer_seq should provide O(logN) order | R. Martinho Fernandes | 12.03.13 06:39 | Ok, that's fair enough. As long as O(1) implementations are nor forbidden ;)
Mit freundlichen Grüßen, Martinho |
| Re: [std-proposals] Re: std::make_integer_seq should provide O(logN) order | Jonathan Wakely | 12.03.13 06:40 | I certainly wouldn't object to O(1), and I'll mention it when the proposal is discussed, but I want to gauge the committee's reaction to the basic feature before requiring compiler magic as well. If the feature is accepted and users consider it important compilers might offer an O(1) make_integer_seq as a Quality of Implementation feature anyway. TBH I was expecting feedback to say that the generic integer_seq<T, T...> template is not needed and I should just choose one of int_seq<int...> or uint_seq<unsigned...> and forget the others, but noone has commented on that part so I'm pleased the feedback has been "this is great, make it faster!" instead :-) |
| Re: [std-proposals] Re: std::make_integer_seq should provide O(logN) order | Mikael Kilpeläinen | 12.03.13 06:54 | 12.3.2013 14:40, Jonathan Wakely kirjoitti:integer_seq<T, T...> is consistent with std::integral_constant<T, T>, except of the integer != integral part. Mikael |