Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98843
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
Date: Sat, 22 Apr 2017 11:40:27 +0000
Message-ID: <CAJaRsPsfWtKbke8VvM-na=vCm0E6T62gmamj2V8sJiHRFB7FLQ@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114098e8d38bdf054dbfd71e
Subject: [RFC] Enable strict_types checking for curl_setopt()
From: colinodell@gmail.com ("Colin O'Dell")

--001a114098e8d38bdf054dbfd71e
Content-Type: text/plain; charset=UTF-8

Hello internals,

I'd like to propose an enhancement to curl_setopt()
<http://php.net/manual/en/function.curl-setopt.php> which is used to
configure a given curl session.  The second argument of this function
defines which option to set and the third argument provides the
corresponding value to use.

Because each option expects the value to be a specific type, it makes sense
to enforce these types in strict type checking mode.  I'd therefore like to
propose that we introduce strict type enforcement inside curl_setopt() when
"declare(strict_types=1);" is being used.

The full details of the proposal, including the proposed patch, can be
found here: https://wiki.php.net/rfc/curl_setopt_strict_types

Huge thanks to Sara Golemon for the idea and creating the patch!

Cheers,

Colin O'Dell
colinodell@gmail.com

--001a114098e8d38bdf054dbfd71e--