Go to file
2019-12-25 20:08:07 +01:00
docs Initial commit 2019-12-24 02:01:46 +01:00
src [Random] add tests 2019-12-25 19:13:06 +01:00
tests/Psl remove @covers annotations 2019-12-25 19:46:58 +01:00
.coveralls.yml add coveralls integration 2019-12-25 19:39:01 +01:00
.gitignore add coveralls integration 2019-12-25 19:39:01 +01:00
.php_cs.dist Initial commit 2019-12-24 02:01:46 +01:00
.scrutinizer.yml add scrutinizer integration 2019-12-25 20:08:07 +01:00
.travis.yml add coveralls integration 2019-12-25 19:39:01 +01:00
composer.json add coveralls integration 2019-12-25 19:39:01 +01:00
LICENSE Initial commit 2019-12-24 02:01:46 +01:00
phpunit.xml.dist fix code coverage output path 2019-12-25 19:51:05 +01:00
psalm.xml Initial commit 2019-12-24 02:01:46 +01:00
README.md add coveralls integration 2019-12-25 19:39:01 +01:00

Psl - PHP Standard Library

Psl is a standard library for PHP, inspired by hhvm/hsl.

The goal of Psl is to provide a consistent, centralized, well-typed set of APIs for PHP programmers.

[![Build Status](https://travis-ci.org/azjezz/psl.svg?branch=master)](https://travis-ci.org/azjezz/psl)
[![Total Downloads](https://poser.pugx.org/azjezz/psl/d/total.svg)](https://packagist.org/packages/azjezz/psl)
[![Latest Stable Version](https://poser.pugx.org/azjezz/psl/v/stable.svg)](https://packagist.org/packages/azjezz/psl)
[![License](https://poser.pugx.org/azjezz/psl/license.svg)](https://packagist.org/packages/azjezz/psl)

Example

<?php

declare(strict_types=1);

use Psl\Str;
use Psl\Iter;

/**
 * @psalm-param iterable<?int> $codes
 */
function foo(iterable $codes): string
{
    return Str\join(Iter\map(
        Iter\filter_nulls($codes), fn($i) => Str\chr($i),
    ), ', ');
}

foo([95, 96, null, 98]);
// 'a, b, d'

Installation

This package doesn't not have a stable release yet, but you can still install it using composer :

$ composer require azjezz/psl:dev-master

Documentation

Documentation is not available yet.

Principles

  • All functions should be typed as strictly as possible
  • The library should be internally consistent
  • References may not be used
  • Arguments should be as general as possible. For example, for array functions, prefer iterable inputs where practical, falling back to array when needed.
  • Return types should be as specific as possible
  • All files should contain declare(strict_types=1);

Consistency Rules

This is not exhaustive list.

  • Functions argument order should be consistent within the library
    • All iterable-related functions take the iterable as the first argument ( e.g. Iter\map and Iter\filter )
    • $haystack, $needle, and $pattern are in the same order for all functions that take them
  • Functions should be consistently named.
  • If an operation can conceivably operate on either keys or values, the default is to operate on the values - the version that operates on keys should have _key suffix (e.g. Iter\last, Iter\last_key, Iter\contains, Iter\contains_key )
  • Find-like operations that can fail should return ?T; a second function should be added with an x suffix that uses an invariant to return T (e.g. Arr\last, Arr\lastx)
  • Iterable functions that do an operation based on a user-supplied keying function for each element should be suffixed with _by (e.g. Arr\sort_by, Iter\group_by, Math\max_by)

License

The MIT License (MIT). Please see LICENSE for more information.