Contrib Tasks

CREATED: <2025-05-01 Thu 20:58>
ID: e5b3474a-ae82-4b67-9f07-808738d691b5

• State "TBD" from [2025-05-01 Thu 20:58]
• State "OUTLINE" from [2025-05-01 Thu 21:01]

• [2025-05-01 Thu 21:02] Discord Lisp#common-lisp

  so I've been thinking about logical pathnames for a bit - it appears
  there is plenty of room for implementation-defined extension in the
  spec (via translate-logical-pathname keyword args) as well as
  load-logical-pathname-translations - what I'd like to do is make some
  recommendations for extending the capabilities in a
  backwards-compatible way that are less geared towards managing
  filesystem conventions between different physical hosts and more
  towards being an easy 'path-finding' tool which is easy for
  programmers to plug custom logic into.
  
  @phoe would this be something a CDR would apply to? alternatively I
  could just work on a patch to submit for sbcl - still need to look at
  if any other impl does something fancy
  

Bike: honestly that's the only thing i use them for, but i'm open to
suggestions. what would you like to have beyond the
logical-pathname-translations interface?

[10:26 PM]ellis: what I'm thinking is some sort of API where you can
provide additional layers of translation, maybe by specifying a
keyword argument args in the form :translate-device (lambda (device)
;; translation? side effects on dynamic vars?) :translate-version..

[10:31 PM]ellis: for load-logical-pathname-translations i like the
idea of a similar situation with a user defined function instead of
relying on 'SYS:SITE;HOST.TRANSLATIONS' - maybe I want to use this in
a p2p discovery service for example and I want to specify a function
which does a remote lookup, parses a response and returns the
appropriate form

[10:33 PM]ellis: right now i'm just experimenting with the
conventional local-projects approach, stuff like 'SYS:TMP' and
'MEDIA:MUSIC', which has kept me busy enough but will find some time
to prototype something out

[10:40 PM]ellis: a few other things that came to mind..  cached/db
access to pathname translation index-based wildcard translation
(sketchy) - (translate-logical-pathname "MEDIA:MUSIC;0"
:translate-wildcard (lambda (x) (aref
*sorted-music-directory-contents* x)))

[10:44 PM]ellis: really makes more sense as a package, like
translate-pathname* but just a shame to waste those keyword args lol

[10:44 PM]ellis: (defvar *default-logical-pathname-translator* 'translate-logical-pathname)

• [2025-05-02 Fri 14:57] initial feedback

  3:48 AM]Isomorphism: Yeah but on the other hand, why not just make a
  dedicated library to your path parsing thing? Generic extensions to
  path resolution is a little scary to me, given that something
  unrelated could suddenly become vulnerable to some injection attack
  
  [9:51 AM]Bike: i would generally be skeptical of a global hook like
  this translator. it's nasty if libraries can rebind or set a variable
  and suddenly logical pathname stuff everywhere breaks, including
  inside the implementation. logical-pathname-translations is sorta
  there already though
  

CREATED: <2025-05-01 Thu 21:15>
ID: 7547601b-97f4-46dd-9d3f-d3b21f8818bc
LICENSE: zlib

• State "RESEARCH" from [2025-05-01 Thu 21:15]
• Note taken on [2025-05-01 Thu 21:17]
  priorities are tests and documentation.
  • 3d-math tests are highest prio

• 3d Math
• Shinmera/3d-math
• Shinmera/verbose
• Shinmera/piping
• https://github.com/Shirakumo/manifolds
• https://github.com/Shirakumo/redist
• https://github.com/Shirakumo/layout
• https://github.com/Shirakumo/lichat-protocol
• https://github.com/Shirakumo/l-hacd
• https://github.com/Shirakumo/hourly

CREATED: <2025-05-01 Thu 22:15>
ID: b26437fd-633c-4ea3-bf73-3b62d72c855c

• State "RESEARCH" from [2025-05-01 Thu 22:15]
• State "WIP" from "RESEARCH" [2025-05-04 Sun 19:38]

CREATED: <2025-05-02 Fri 13:15>
ID: 038c7ad6-6e12-48dc-823c-5a5ad948839c

• State "TBD" from [2025-05-02 Fri 13:15]

CREATED: <2025-05-02 Fri 13:15>
ID: d170a060-6ec9-4d0d-b571-2dfe634862b0

• State "TBD" from [2025-05-02 Fri 13:15]

CREATED: <2025-05-03 Sat 20:13>
ID: bf829af6-bbb8-4e64-8839-41f0aac733f2

• State "RESEARCH" from [2025-05-03 Sat 20:13]
• State "WIP" from "RESEARCH" [2025-05-04 Sun 19:38]