CppCon 2018 Program Submission

Use this form for regular conference program submissions.


Please only include presenters that will attend. Co-authors and other contributors not attending can be recognized in your presentation.

Add Speaker

As you would like it to appear in the conference program.

For conference use only. We will not share this with third parties except as required to run the conference.

Optional. We will include this when tweeting about your session.

The submitter's school, company, or other affiliation.

The submitter's home country.

Please use the third person: "he" or "she" rather than "I" or "me."
Each submitter will be given the opportunity to edit their conference bio to include a photo, website, and public social media contacts. For now, we just ask to help the Program Committee better understand your background.

Mentoring responses are not used by the Program Committee when evaluating submissions.

Submission Info

The information in this section is directed to attendees and must be suitable for the conference web site.

Please use AP style title case. Acronyms should be all uppercase. Code elements such as keywords, function names, etc should be as would be written in code. Subtitles should be set off with colons, not dashes, using a space after, but not before the colon. See Boost library naming rules.
For example, "My Adventures With Boost.Asio: return to Sender"

Please include a comma separated list of at least three tags for the session. Use lower case except for proper nouns and acronyms. Strive for the general, not the specific:"testing," rather than "unit tests." Spell out acronyms unless they are more likely to be understood as acronyms: "artificial intelligence" rather than "AI" and "GUI" rather than "graphical user interface."
For example, "games,performance,cross platform,I/O,C compatibility,HTML"
For additional information, see our tagging guide.

Select a session type or enter your own.

Standard sessions are 60 minutes. Preferred, min, and max can all be the same value.


If your presentation spans levels, such as intermediate to advanced, check all that apply.

Examples: library authors, application developers, game developers, etc. A quality description helps your audience find your submission. Please keep it short and sweet. Full sentence not required.


As it should appear in the program. About one to three paragraphs.
This is your pitch to both the Program Committee and to potential attendees about why they should see your presentation.
Try to answer the reader's questions, Why is this important to me? and What will I learn?

To the Program Committee

The information in this section is not published on the website as part of the conference program, but is intended only for the Program Committee.

(encouraged, but not required)

List material that will be available for on-line distribution: (slides, source code, etc.)

Support requirements are not used by the Program Committee when evaluating submissions.

Specify any special (AV or other) requirements for your session.

You'll not be held to this—we understand that this is a snapshot in time.

If you’ve presented this talk before, please tell us where and when.
We do accept submissions of sessions presented at other conferences.
Repeats of sessions from a previous CppCon are accepted, but, because sessions are recorded, the bar for repeats is higher than for new sessions.
Repeats of successful workshops are always welcome.

Please include the URL of a video of you giving a technical presentation (as similar as possible to your proposal).
We do accept submissions from first time presenters, so this is optional, but if you have a recording of yourself presenting, it helps the PC evaluate your presentation abilities.
You may use a video that you've made and posted yourself. If no such video exists, consider a link to a slide deck that you've created.
Feel free to add any comments you feel necessary about this material.

Anything you'd like the Program Committee to know about your talk.