Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112817 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 79846 invoked from network); 8 Jan 2021 12:46:52 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Jan 2021 12:46:52 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D13C31804DD for ; Fri, 8 Jan 2021 04:23:49 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-io1-f48.google.com (mail-io1-f48.google.com [209.85.166.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 8 Jan 2021 04:23:49 -0800 (PST) Received: by mail-io1-f48.google.com with SMTP id r9so9523900ioo.7 for ; Fri, 08 Jan 2021 04:23:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0DNnZOSTs+sm9fIoJiugV+HTb1vZpxgaav/yeMYk/5Y=; b=QtCy3tONQwODtr7fysy9KZG7VrhbfGlceVya/DF/DWaYnJr+JJI3adh/486cDh4/uy B6eK4l5Jr8+SqxZN3XaNCdIkTdQUUYAOjF2Mez+gZYXPGrZJqnZ2wDg1IwB7TVTZ1tCT iUsiwnQFhdy//I1D2OB0cfUZnGduP/sVoWTfSo7lonkAkMAkwcUNcGMFAVA0kdv9sf5M EE9waH2QJW1peLihQj9rNrmQPW3fdeZ3gQgFW7Vy/UsYS0EcozhinTWJ5vvKD1u12HEy 1T6JAhRcqEaat1nFCfXeNiy++M5qIMHhs0QfitL7jEMvZ4tRSLnOR9ha4DAZQyFAdxrB xENw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0DNnZOSTs+sm9fIoJiugV+HTb1vZpxgaav/yeMYk/5Y=; b=Pf+psr6Jmtr/HV2eahxGQ8bW6boU5KCj9P6eed05kGmyc6XpQNl1pA+8P2QrjqM6ik 3jMyK02n8nCg666lcIXLdr7+8vpPyAiYd5zxKZ5uLNVtNLfrn0KH3ZMISGstYY6U6QNe nR/nfI0aCLC+kuyOrzHsOQfY9pByAz6/4U463WX8tCdO2BagP6Qc7GgFJ7/rA+v3vMsX XP/W708iXJx4YQWDw76mu1z5c5GWgfoMZWpOI+BrWetZ9feL7zPwnwYLL607AlrgFzvY jQ0/d3ILExE4EZ67hGJRTIRUAxcI1HztkmaWt/vpIxxZpb6v0W+ZQU8S/eHiQQ/HFQdG cQdA== X-Gm-Message-State: AOAM532xVaNsBcJkTIn0nFzlX/+eDeIIPXPj7LF8UNrY4+kCuvgLobvr RaZ+KwxzwWTGL5tBjCk0sfnV8S07BFPXttlQJKM= X-Google-Smtp-Source: ABdhPJzqQ9eNXSIMSIS6hCBKw+vGoawhjOMSPqOL6wBgK7U80dP3ggWIHUJV43uB59wO3rtXduR9BqIIvsXh41RLYns= X-Received: by 2002:a6b:f714:: with SMTP id k20mr5161409iog.70.1610108624891; Fri, 08 Jan 2021 04:23:44 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 8 Jan 2021 13:23:32 +0100 Message-ID: To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= Cc: Nikita Popov , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000a2f5a205b862a06f" Subject: Re: [PHP-DEV] [RFC] Bundling ext/simdjson into core From: ocramius@gmail.com (Marco Pivetta) --000000000000a2f5a205b862a06f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey M=C3=A1t=C3=A9, On Fri, Jan 8, 2021 at 1:20 PM M=C3=A1t=C3=A9 Kocsis wrote: > In the meanwhile I also realized that there are just too many unknowns > currently with this extension, so I cancelled my initial plans of adding > ext/simdjson as a core extension. > Since the majority of issues revolve around uncertainty/compatibility, is there perhaps a way for using the extension with an "overload `json_encode()` and `json_decode()` mode" (remember mbstring?), so that brave bleeding edge users can experiment with it as an opt-in replacement? That would certainly allow for some more precise field testing over the next few years. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ --000000000000a2f5a205b862a06f--