docs(3p/lisp/mime4cl): add clear warning about current state
I'm not really describing what the problem here is because I don't think a writeup is really useful. It would just be speculation and I don't need to syncronize my efforts with anyone at the moment, so it's best to keep those notes offline. Basically, the next problem I want to tackle is that the initial parsing of a multipart message (to get the number, types, offsets etc. of the different parts) is very slow. This is because READ-LINE on a FLEXI-STREAM dispatches to READ-CHAR which is laughably slow. Change-Id: Ia5d6e335abb23639cfe9c2149ead99ffa5dbbcf5 Reviewed-on: https://cl.tvl.fyi/c/depot/+/12936 Reviewed-by: sterni <sternenseemann@systemli.org> Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
This commit is contained in:
parent
bd4da5f444
commit
ee9c3c254c
1 changed files with 5 additions and 2 deletions
7
third_party/lisp/mime4cl/README.md
vendored
7
third_party/lisp/mime4cl/README.md
vendored
|
@ -9,8 +9,11 @@ website](http://wcp.sdf-eu.org/software/#mime4cl) can still be accessed.
|
|||
The depot version has since diverged from upstream. Main aims were to improve
|
||||
performance and reduce code size by relying on third party libraries like
|
||||
flexi-streams. It is planned to improve encoding handling in the long term.
|
||||
Currently, the library is being worked on intermittently and not very well
|
||||
tested—**it may not work as expected**.
|
||||
Work towards this happens intermittently.
|
||||
|
||||
WARNING:
|
||||
mime4cl currently doesn't have a _comprehensive_ test suite
|
||||
and decidedly lacks performance.
|
||||
|
||||
## Differences from the original version
|
||||
|
||||
|
|
Loading…
Reference in a new issue