Followups from the new C++/WinRT #19406

Open
opened 2026-01-31 06:42:20 +00:00 by claunia · 1 comment
Owner

Originally created by @DHowett on GitHub (Feb 18, 2023).

Interesting things we could do after #14869 landed:

### Tasks
- [x] remove all `InitializeComponent` calls - they do it automatically
- [ ] use `std::optional`<->`IReference` automatic binding
- [x] use `std::format` support (!) for json/uri/hostname/http stuff/all `IStringable`s
- [ ] potentially move to `/await:strict` for C++20 coroutines
Originally created by @DHowett on GitHub (Feb 18, 2023). Interesting things we could do after #14869 landed: ```[tasklist] ### Tasks - [x] remove all `InitializeComponent` calls - they do it automatically - [ ] use `std::optional`<->`IReference` automatic binding - [x] use `std::format` support (!) for json/uri/hostname/http stuff/all `IStringable`s - [ ] potentially move to `/await:strict` for C++20 coroutines ```
claunia added the Help WantedIssue-TaskProduct-MetaArea-CodeHealth labels 2026-01-31 06:42:20 +00:00
Author
Owner

@DHowett commented on GitHub (Mar 29, 2023):

We should probably not upset the delicate balance of InitializeComponent calls, because removing them can make it so that XAML things we reference from the ctor break.

The only ones of these that really have legs are:

  • optional <-> IReference binding
  • await:strict

I checked the others off after an audit.

@DHowett commented on GitHub (Mar 29, 2023): We should probably not upset the delicate balance of InitializeComponent calls, because removing them can make it so that XAML things we reference from the ctor break. The only ones of these that really have legs are: - optional <-> IReference binding - await:strict I checked the others off after an audit.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19406