Add Swift scheduling exercice

[resu-xuniL]

Another exercice for validation.

[mk-mxp]

Thanks a lot for your contribution! I'm not totally pleased with the class interface, as it makes the problem look like a functional problem (no constructor args, one method to call). But we go with it when you do not want to invest more time / effort.

The introduction sounds more like "one meeting start given, many delivery dates derived" to me. Based on that, I'd suggest changing the implementation to this interface:

class SwiftScheduling
{
    public function __construct(DateTime $meetingStart)
    {
        throw new \BadMethodCallException(sprintf('Implement the %s method', __FUNCTION__));
    }

    public function deliveryDate(string $description): DateTime
    {
        throw new \BadMethodCallException(sprintf('Implement the %s method', __FUNCTION__));
    }
}

You can use constructor promotion to ease implementation.

[resu-xuniL]

I hope I correctly understood your proposal :)

[mk-mxp]

Yes, that's what I had in mind. Thanks for your effort!

[resu-xuniL]

You're welcome! thanks to you ...