What Comes to Mind (old posts, page 10)

Concept Maps using C++23 Library Tech

2024-05-19 11:51

Abstract

C++0x Concepts had a feature Concept Maps that allowed a set of functions, types, and template definitions to be associated with a concept and the map to be specialized for types that meet the concept.

This allowed open extension of a concept.

Slides from C++Now 2023 Async Control Flow

2024-05-18 18:27

Using Sender/Receiver for Async Control Flow

Steve Downey

These are the slides, slightly rerendered, from my presentation at C++Now 2023.

Abstract

How can P2300 Senders be composed using sender adapters and sender factories to provide arbitrary program control flow?

How do I use these things?

Where can I steal from?

Some Informal Remarks Towards a New Theory of Trait Customization

2023-12-24 00:00

A Possible Technique

constexpr bool g(int lhs, int rhs) {
    auto& op = partial_eq<int>;
    return op.ne(lhs, rhs);
}

Compiler Explorer with Supporting Code A trait is defined as a template variable that implements the required operations. Implementation of those operations is possible via a variety of techniques, but existence is concept checkable. It might prove useful to explicitly opt in to a sufficiently generic trait. The technique satisfies the openness requirement, that the trait can be created independently of the type that models the trait. There can still only be one definition, but this enables opting std:: types into new traits, for example. It also doesn't universally grab an operation name. The trait variable is namespaceable. Syntax isn't really awesome, but not utterly unworkable.

Special Blocks and Emacs Org-mode Export

2021-12-03 00:00

Document number:
Date: 2021-12-03
Author: Steve Downey <sdowney2@bloomberg.net>, <sdowney@gmail.com>
Audience: WG21 Emacs Authors

Abstract: Making emacs org-mode more usable for writing WG21 papers.

A local CMake workflow with Docker

2021-10-03 00:00

l#+BLOG: sdowney

An outline of a template that provides an automated workflow driving a CMake project in a docker container.

This post must be read in concert with https://github.com/steve-downey/scratch of which it is part.

Routine process should be automated

Building a project that uses cmake runs through a predictable lifecycle that you should be able to pick up where you left off without remembering, and for which you should be able to state your goal, not the step you are on. make is designed for this, and can drive the processs.