Changes between Version 11 and Version 12 of SoC2014

Timestamp:

Jan 18, 2014, 5:02:35 PM (9 years ago)

Author:

viboes

Comment:

Added some projects.

SoC2014

@@ -106 +106 @@
 This project would be mentored by Niall Douglas (http://www.nedprod.com/). Due to limits on free time, I would only be able to mentor one student this summer, and I generally provide a programming test based on AFIO to students whose have submitted proposals to ensure that their coding ability is minimally sufficient to be able to attempt a GSoC. Benefits for the student of a successful GSoC in this area are many: high performance async programming experience is very desirable in the marketplace right now, and getting your name attached to authorship of a Boost library is a shining bright light on a resume which will stand to your career for years to come. You will gain bleeding edge experience programming exclusively in C++11 across the main toolsets of Visual Studio, GCC and clang AND writing portable code for the main operating system platforms of Microsoft Windows, Linux, and BSD/OS X - again, all very desirable skills to have in the marketplace. For those of you looking at a career in computer science research, and depending on the success of your outcomes, you may even be able to pass peer review to present your work at the C++ Now conference held annually in May. Good luck with your GSoC applications!
 
+=== Boost.Functional/Invoke === 
+
+Provide a boost::invoke function implementation of the c++11 definition of INVOKE for c++11 and C++03 compilers based on the interface defined in [1]. [2] could be taken in consideration.
+
+This project could be mentored by Vicente J. Botet Escriba
+
+
+[1] http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3727.html
+
+[2] https://github.com/boostorg/thread/tree/develop/include/boost/thread/detail/invoke.hpp
+
+
+=== Boost.Thread/WorkStealingThreadPool === 
+
+Provide a boost::work_stealing_thread_pool class scheduling arbitrary functions based on the interface defined in [1]. [2] should be taken in consideration. 
+
+[1] https://github.com/boostorg/thread/tree/develop/include/boost/thread/executors
+
+[2] http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3562.pdf
+
+This project could be mentored by Vicente J. Botet Escriba
+
+=== Boost.Thread/SchedulerExecutor === 
+
+Provide boost::scheduled_executor implementations base on the C++ proposal [1] and the draft implementation in [2]. 
+
+[1] http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3562.pdf
+
+[2] https://github.com/boostorg/thread/tree/develop/include/boost/thread/executors
+
+This project could be mentored by Vicente J. Botet Escriba
+
+
+=== Boost.FixedPoint === 
+
+Provide an implementation of a FixedPoint library based on [1].
+
+A prototype with a different interface is available at [2]
+
+[1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3352.html
+
+[2] https://svn.boost.org/svn/boost/sandbox/fixed_point/
+
+=== Boost.Chrono/Date === 
+
+Provide an implementation of a Date library based on [1].
+
+A prototype with a different interface is available also at [2].
+
+[1] https://svn.boost.org/svn/boost/sandbox/chrono_date/libs/date/doc/date.html
+
+[2] https://svn.boost.org/svn/boost/sandbox/chrono_date/
+
+This project could be mentored by Vicente J. Botet Escriba
+
+=== Boost.Exception/StackUnwinding === 
+
+Make a real Boost library the StackUnwinding library [1] from Evgeny Panasyuk ready for review.
+
+[1] https://github.com/panaseleus/stack_unwinding#d-style-scope-guardsactions
+
+=== Boost.Pipelines === 
+
+Provide boost::pipelines implementations base on the C++ Pipelines proposal [1] and the Google implementation in [2]  
+
+[1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3534.html
+[2] https://code.google.com/p/google-concurrency-library/source/browse/include/pipeline.h 
+
+This project could be mentored by Vicente J. Botet Escriba
+
+=== Moving Boost to Boost.Move === 
+
+There a re a lot of Boost libraries that don't support move semantics.
+It would be nice if one student propose to adapt the some of the existing libraries.
+
+The idea is to use Boost.Move so that an emulation is provided for compilers not supporting rvalue references.
+
+Some of the libraries (let me know if I'm wrong are). My priority is given between [], lower numbers means higher priority. Of course others would have others priorities:
+
+C++11
+* [0] Tuple or * Fusion/tuple (it seems that it support or will support c++11 move semantics but don't use Boost.Move)
+* [0] Bind
+* [1] Function
+* [2] SmartPtr
+* [8] Array ?
+
+Accepted for C++14
+* [5] optional
+
+Having an active proposal for C++1y
+* [3] Heaps
+* [6] Any
+* [7] Variant
+
+
+Other
+* [4] LockFree
+* [9] Parameters
+* [10] Signals?
+
+Please help me to complete this list.
+
+Adding constexpr and noexcept would be welcome also.
+
+This project could be mentored by Vicente J. Botet Escriba
+
 == Ideas ==