Changes between Version 16 and Version 17 of SoC2015

Timestamp:

Feb 20, 2015, 5:36:07 PM (8 years ago)

Author:

Thorsten Ottosen

Comment:

new proposal

SoC2015

@@ -188 +188 @@
 
 Submission of the programming test should be via copying and pasting what you wrote into the end of the proposal you submit to Google Melange.
+
+=== 5. Enhanced vector and deque containers ===
+Potential mentors: Thorsten Ottosen
+
+
+==== Background ====
+
+For certain applications the standard constainers std::vector and std::deque are not too easy to work or may induce
+unnecessary overhead. For example, std::vector lacks an O(1) time push_front and std::deque allows you no way
+of controlling the size of the underlying segments. This limits their usability in certain contexts, especially if you
+want to have optimal performance.
+
+==== GSoC project proposal ====
+
+Write full-fledged and enhanced C++11 versions of std::deque and std::vector with extra functionality that
+gives the programmer more control over buffers, segments and iteration.
+
+==== Programming competency test ====
+
+Write a small vector-like C++11 container. The capacity is set in the constructor. push_back throws when the buffer is full.
+It should work efficiently with both strings and ints. push_back should have the strong exception-safety gusrantee. The class may not
+leak any resources. Iterators may be pointers. Put noexcept on every function where it makes sense. Write unit-tests for all
+functions. Write a unit-test that proves that your implementation of push_back has the strong exception-safety guarantee.
+
 
 == Self-contained standalone GSoC Projects (no competency test) ==