Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118142
MIME-Version: 1.0
References: <CAOfKkdTjPiZHnSHuag_+fmFK-1Advh2-vfDgbJBXEmK=72NB0g@mail.gmail.com>
 <7CB0EB0B-700D-49F6-8223-00A9B16F463B@php.net>
In-Reply-To: <7CB0EB0B-700D-49F6-8223-00A9B16F463B@php.net>
Date: Thu, 30 Jun 2022 12:48:02 -0400
Message-ID: <CAOfKkdQJUww10XkdcPx9AvAe=w=T8mS1MW6oJ=itzLp4x7L1jA@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001abd3f05e2ad0958"
Subject: Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API
From: pierrick@php.net (Pierrick Charron)

--0000000000001abd3f05e2ad0958
Content-Type: text/plain; charset="UTF-8"

Hi all,


> - The new CurlUrl class should probably be immutable from the start. It
> was my biggest mistake not to do that with DateTime.
>
>
After thinking about it and some discussions, I followed Derick's
recommendation and therefore changed the RFC to make the CurlUrl class
immutable. All the setters were replaced by new `with*` methods.
For example setHost is now withHost and will return a new object with the
host modified. This will prevent confusing behavior where the CurlUrl
object would be unintentionally modified after being attached to a
CurlHandle.

Pierrick

--0000000000001abd3f05e2ad0958--