Should tools support .t6 extension?

Raku / user-experience

Identifying issues in and improving the Raku user experience

Artistic License 2.0

25 stars 5 forks source link

Should tools support .t6 extension? #36

Closed AlexDaniel closed 5 years ago

AlexDaniel commented 5 years ago

See https://github.com/perl6/doc/issues/2576 for the previous discussion.

Affected tools and other things:

[x] zef
[x] App::Mi6
[x] App::Assixt
[ ] prove (no ticket)
[x] prove6
[x] travis
[x] https://github.com/perl6/modules.perl6.org

Also:

[ ] docs https://github.com/perl6/doc/issues/2576
[ ] wikipedia?
[ ] github linguist (no ticket)
[ ] https://fileinfo.com/ ? Note that it already knows about .p6, but not about .pl6 or .pm6 (there's an entry for .pm6 associating it with a discontinued product)

jmaslak commented 5 years ago

I'll submit a PR for Mi6 this evening.

Leont commented 5 years ago

This also affects prove6.

Actually, I'm not sure prove should be changed. I don't think it's really sense to keep adapting perl5 toolchain to be more suitable for perl6 purposes, when there is a perl6 equivalent available.

Leont commented 5 years ago

This also affects prove6.

An implementation of this is part of the dev branch :-)

Leont commented 5 years ago

App::Mi6 currently writes a .travis.yml that doesn't take this into account

Leont commented 5 years ago

App::Mi6 currently writes a .travis.yml that doesn't take this into account

This has been fixed in https://github.com/skaji/mi6/commit/017c8dc43fa5b7a5e09d9cc7de7faeaa8661faad

AlexDaniel commented 5 years ago

This no longer matters.

AlexDaniel commented 5 years ago

Although, similar approach should be used for new extensions, but I believe creating a new ticket is a good idea.