array_walk adventures

I noticed something weird today that I thought I’d share. Before you get too excited know that I only am supplying the questions this time. I don’t have a great answer to why this thing is happening.

So I’ve been on a quest to learn more php functions lately and I came across array_walk. When I read the description I immediately thought, “Oh it allows you to keep the original keys? This must be what laravel’s map function uses. I was wrong though. Here is Laravel’s map function.

    /**
     * Run a map over each of the items in the array.
     *
     * @param  array  $array
     * @param  callable  $callback
     * @return array
     */
    public static function map(array $array, callable $callback)
    {
        $keys = array_keys($array);

        try {
            $items = array_map($callback, $array, $keys);
        } catch (ArgumentCountError) {
            $items = array_map($callback, $array);
        }

        return array_combine($keys, $items);
    }

So you see it runs array_keys to get the keys, does array_map with the callback and then does an array_combine at the end. Immediately I thought, well array_walk would be way more efficient here! I did a quick refactor and got this-

    /**
     * Run a map over each of the items in the array.
     *
     * @param  array  $array
     * @param  callable  $callback
     * @return array
     */
    public static function map(array $array, callable $callback)
    {
        try {
            array_walk(
              $array,
              function (&$val, $key) use ($callback) {
                $val = $callback($val, $key);
              },
            );
        } catch (ArgumentCountError) {
            array_walk(
              $array,
              function (&$val) use ($callback) {
                $val = $callback($val);
              },
            );
        }

        return $array;
    }

Believe it or not this works! array_walk works a little differently in that you pass the value of each element through as a pointer to the original value and then you modify the original array as you go. So instead of returning values that update the value in a new array, you just set the value that is pointing at the value in the array to update the original array. In my mind this should be faster. There is one less iteration through the loop (no combine step) but in my experience it was slightly slower.

I ran the laravel test suite 2 or 3 times and consistently got 1min 22 sec and ~200 milliseconds. When I ran with array_walk I got 1min 22sec and ~900 milliseconds. I know we are splitting hairs here but I’m really curious why array_walk is slower when its only iterating through the array once. And then the follow up question is would there ever be a threshold where array_walk would start to be faster?

Using Clerk.com with a laravel backend part 2

In this video we are going to be adding on a laravel backend and decoding the jwt that we passed from our frontend in the previous video.

Using Clerk.com with a laravel backend part 1

In this video I’m going to show you how to use laravel as a backend on a frontend set up with Clerk authentication. We will be using Remix on the frontend. We will set up clerk auth, then start the process of packaging up the jwt to send to our Laravel backend. In part 2 we will discuss how you can decode the jwt, verify it and use Laravel in a stateless manner.