What are the concrete differences between WebKit C++ conventions and the
current swift-format configuration
https://github.com/WebKit/WebKit/blob/main/.swift-format ?

I see that newly added Swift code in the WebKit repository does not differ
much from the existing C++ conventions.
I wonder about the details of what will change if we use swift-format.

--
Tetsuharu OHZEKI
[email protected]

2026年11月5日(木) 3:04 Abrar Protyasha via webkit-dev <
[email protected]>:

> I want WebKit to adopt suggested/conventional Swift style, maybe with some
> well-reasoned (and agreed on) project-specific tweaks. I don’t know if
> there is added value in having source files of two different languages
> follow one style? Swift is vaguely C-lang styled, but otherwise it’s a very
> different programming language and we don’t necessarily need it to look the
> same as C++.
>
> There may be specific issues with the existing Swift style format enforced
> in the project that we may want to debate, but for the most part it seems
> best to just use as much of the defaults opined by swift-format.
>
> > On Nov 4, 2026, at 4:46 AM, Jean-Yves Avenard via webkit-dev <
> [email protected]> wrote:
> >
> >
> >
> >> On 4 Nov 2026, at 2:55 am, Ryosuke Niwa via webkit-dev <
> [email protected]> wrote:
> >>
> >> Hi all,
> >>
> >> As we adopt more Swift in cross-platform parts of WebKit, we need to
> decide what kind of coding styles we’d adhere to.
> >>
> >> I suggest that we adopt the existing C++ coding style guidelines for
> Swift with one modification: curly braces around a single-line statement
> are mandatory in Swift.
> >>
> >> Thoughts?
> >
> > +1
> >
> > _______________________________________________
> > webkit-dev mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
>
> _______________________________________________
> webkit-dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
webkit-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to