{"size": 19884, "ext": "scrbl", "max_stars_repo_path": "doc/srfi.scrbl", "max_stars_repo_name": "christoff-buerger/sagittarius-scheme", "max_stars_repo_stars_event_min_datetime": "2015-11-07T07:13:35.000Z", "max_stars_repo_stars_event_max_datetime": "2022-02-15T03:35:14.000Z", "max_issues_repo_path": "doc/srfi.scrbl", "max_issues_repo_name": "christoff-buerger/sagittarius-scheme", "max_issues_repo_issues_event_min_datetime": "2016-04-28T21:59:59.000Z", "max_issues_repo_issues_event_max_datetime": "2021-07-01T08:42:21.000Z", "max_forks_repo_path": "doc/srfi.scrbl", "max_forks_repo_name": "christoff-buerger/sagittarius-scheme", "max_forks_repo_forks_event_min_datetime": "2016-12-28T12:41:23.000Z", "max_forks_repo_forks_event_max_datetime": "2020-02-26T20:52:02.000Z"}
{"max_stars_count": 39, "max_issues_count": 3, "max_forks_count": 4, "avg_line_length": 47.3428571429, "max_line_length": 120, "alphanum_fraction": 0.672651378}
@; -*- mode:scribble; coding: utf-8 -*-

@section[:tag "srfi"]{Supporting SRFIs}

SRFI is a great libraries, so there is no reason not to support. Without
exception Sagittarius also supports several SRFIs. The following list is the
supported SRFI. Documents are not written for now. So if you need to refer the
functions, please look for SRFI's site. I might write it later.

For now, I just put pointer to @hyperlink[:href "http://srfi.schemers.org/"]{the SRFI's web site}

@table[]{
@tr{@th{SRFI number} @th{Library name}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-0/srfi-0.html"]{SRFI-0}}
    @td{(srfi :0 cond-expand)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-1/srfi-1.html"]{SRFI-1}}
    @td{(srfi :1 lists)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-2/srfi-2.html"]{SRFI-2}}
    @td{(srfi :2 and-let*)}}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-4/srfi-4.html"]{SRFI-4}}
    @td{(srfi :4 numeric-vectors)
        This SRFI also contains reader macro described below this section.
    }}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-6/srfi-6.html"]{SRFI-6}}
    @td{(srfi :6 basic-string-ports)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-8/srfi-8.html"]{SRFI-8}}
    @td{(srfi :8 receive)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-11/srfi-11.html"]{SRFI-11}}
    @td{(srfi :11 let-values)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-13/srfi-13.html"]{SRFI-13}}
    @td{(srfi :13 strings)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-14/srfi-14.html"]{SRFI-14}}
    @td{(srfi :14 char-set)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-16/srfi-16.html"]{SRFI-16}}
    @td{(srfi :16 case-lambda)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-17/srfi-17.html"]{SRFI-17}}
    @td{(srfi :17 generalized-set!)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-18/srfi-18.html"]{SRFI-18}}
    @td{(srfi :18 multithreading)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-19/srfi-19.html"]{SRFI-19}}
    @td{(srfi :19 time)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-22/srfi-22.html"]{SRFI-22}}
    @td{This SRFI does not provide any library.}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-23/srfi-23.html"]{SRFI-23}}
    @td{(srfi :23 error)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-25/srfi-25.html"]{SRFI-25}}
    @td{(srfi :25 multi-dimensional-arrays)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-26/srfi-26.html"]{SRFI-26}}
    @td{(srfi :26 cut)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-27/srfi-27.html"]{SRFI-27}}
    @td{(srfi :27 random-bits)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-29/srfi-29.html"]{SRFI-29}}
    @td{(srfi :27 localization)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-31/srfi-31.html"]{SRFI-31}}
    @td{(srfi :31 rec)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-37/srfi-37.html"]{SRFI-37}}
    @td{(srfi :37 args-fold)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-38/srfi-38.html"]{SRFI-38}}
    @td{(srfi :38 with-shared-structure)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-39/srfi-39.html"]{SRFI-39}}
    @td{(srfi :39 parameters)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-41/srfi-41.html"]{SRFI-41}}
    @td{(srfi :41 streams)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-42/srfi-42.html"]{SRFI-42}}
    @td{(srfi :42 eager-comprehensions)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-43/srfi-43.html"]{SRFI-43}}
    @td{(srfi :43 vectors)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-45/srfi-45.html"]{SRFI-45}}
    @td{(srfi :45 lazy)}}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-49/srfi-49.html"]{SRFI-49}}
    @td{(srfi :49)

        The library exports @code{srfi-49-read}, @code{srfi-49-load} procedures.
        And also be able to replace reader, For more detail, see
@secref["lib.sagittarius.reader"]{(sagittarius reader) - reader macro library}.}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-57/srfi-57.html"]{SRFI-57}}
    @td{(srfi :57 records)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-60/srfi-60.html"]{SRFI-60}}
    @td{(srfi :60 integer-bits)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-61/srfi-61.html"]{SRFI-61}}
    @td{This SRFI is supported by builtin @code{cond}}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-64/srfi-64.html"]{SRFI-64}}
    @td{(srfi :64 testing)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-69/srfi-69.html"]{SRFI-69}}
    @td{(srfi :69 basic-hash-tables)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-78/srfi-78.html"]{SRFI-78}}
    @td{(srfi :78 lightweight-testing)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-86/srfi-86.html"]{SRFI-86}}
    @td{(srfi :86 mu-and-nu)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-87/srfi-87.html"]{SRFI-87}}
    @td{(srfi :87 case)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-98/srfi-98.html"]{SRFI-98}}
    @td{(srfi :98 os-environment-variables)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-99/srfi-99.html"]{SRFI-99}}
    @td{(srfi :99 records)}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-100/srfi-100.html"]{SRFI-100}}
    @td{(srfi :100 define-lambda-object)
    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :100)}. So for the portability it's better to use the
    @code{(srfi :100)}.

    The name @code{define-lambda-object} is taken from the SRFI name.}}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-101/srfi-101.html"]{SRFI-101}}
    @td{(srfi :101 random-access-lists)
    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :101)}. So for the portability it's better to use the
    @code{(srfi :101)}.

    The name @code{random-access-lists} is taken from the sample
    implementation.}}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-105/srfi-105.html"]{SRFI-105}}
    @td{(srfi :105)

    The library exports @code{curly-infix-read} and @code{neoteric-read}
    procedures. These procedures read SRFI-105 the infix style code that
    SRFI-105 specifying. And this also exports reader macros, you can
    activate it with @code{#!read-macro=srfi/:105} or 
    @code{#!read-macro=curly-infix}.

    Even though the specification said it MUST support @code{#!curly-infix},
    however the library just ignore and not activate the reader macros. So
    you need to explicitly write the one mentioned above. To keep your code
    portable between implementations that support this SRFI, you need to write
    both style as following;
@codeblock{
;; write both
#!read-macro=curly-infix
#!curly-infix
}
    The order doesn't matter, Sagittarius just ignores the latter style.
    }}
@tr{@td{@hyperlink[:href "http://srfi.schemers.org/srfi-106/srfi-106.html"]{SRFI-106}}
    @td{(srfi :106 socket)}}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-110/srfi-110.html"]{SRFI-110}}
    @td{(srfi :110)

    The library exports a replacible reader. To use it write following
    hash-bang directives.
@codeblock{
;; write both for compatibility
#!reader=sweet
#!sweet
}
    The order doesn't matter, Sagittarius just ignores the latter style.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-111/srfi-111.html"]{SRFI-111}}
    @td{(srfi :111 boxes)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :111)}. So for the portability it's better to use the
    @code{(srfi :111)}.

    The name @code{boxes} is taken from R7RS-large library name.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-112/srfi-112.html"]{SRFI-112}}
    @td{(srfi :112 inquery)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :112)}. So for the portability it's better to use the
    @code{(srfi :112)}.

    The name @code{inquery} is taken from R7RS-large library name.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-113/srfi-113.html"]{SRFI-113}}
    @td{(srfi :113 sets)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :113)}. So for the portability it's better to use the
    @code{(srfi :113)}.

    The name @code{sets} is taken from its name.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-114/srfi-114.html"]{SRFI-114}}
    @td{(srfi :114 comparators)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :114)}. So for the portability it's better to use the
    @code{(srfi :114)}.

    The name @code{comparators} is taken from its name.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-115/srfi-115.html"]{SRFI-115}}
    @td{(srfi :115 regex)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-116/srfi-116.html"]{SRFI-116}}
    @td{(srfi :116 ilists)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :116)}. So for the portability it's better to use the
    @code{(srfi :116)}.

    The name @code{ilists} is taken from sample implementation.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-117/srfi-117.html"]{SRFI-117}}
    @td{(srfi :117 list-queues)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-120/srfi-120.html"]{SRFI-120}}
    @td{(srfi :120 timer)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :120)}. So for the portability it's better to use the
    @code{(srfi :120)}.

    The name @code{timer} is taken from sample implementation.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-121/srfi-121.html"]{SRFI-121}}
    @td{(srfi :121 generators)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :121)}. So for the portability it's better to use the
    @code{(srfi :121)}.

    The name @code{generators} is taken from sample implementation.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-123/srfi-123.html"]{SRFI-123}}
    @td{(srfi :123 generic-ref)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :123)}. So for the portability it's better to use the
    @code{(srfi :123)}.

    The name @code{generic-ref} is taken from the SRFI discussion.
    @hyperlink[:href "http://srfi-email.schemers.org/srfi-123/msg/2905143"]{Re: SRFI-97 name}
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-124/srfi-124.html"]{SRFI-124}}
    @td{(srfi :124 ephemerons)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :124)}. So for the portability it's better to use the
    @code{(srfi :124)}.

    The name @code{ephemerons} is taken from the example implementation.

    Current implementation of ephemerons has the same issue as the one 
    Chibi has. It is described in the SRFI document.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-125/srfi-125.html"]{SRFI-125}}
    @td{(srfi :125 hashtables)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-126/srfi-126.html"]{SRFI-126}}
    @td{(srfi :126 r6rs-hashtables)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-127/srfi-127.html"]{SRFI-127}}
    @td{(srfi :127 lazy-sequences)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-128/srfi-128.html"]{SRFI-128}}
    @td{(srfi :128 comparators)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-129/srfi-129.html"]{SRFI-129}}
    @td{(srfi :129 titlecase)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-130/srfi-130.html"]{SRFI-130}}
    @td{(srfi :130 string-cursors)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-131/srfi-131.html"]{SRFI-131}}
    @td{(srfi :131 records)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-132/srfi-132.html"]{SRFI-132}}
    @td{(srfi :132 sorting)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-133/srfi-133.html"]{SRFI-133}}
    @td{(srfi :133 vectors)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-134/srfi-134.html"]{SRFI-134}}
    @td{(srfi :134 ideque)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :134)}. So for the portability it's better to use the
    @code{(srfi :134)}.

    The name @code{ideque} is taken from sample implementation.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-135/srfi-135.html"]{SRFI-135}}
    @td{(srfi :135 texts)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :134)}. So for the portability it's better to use the
    @code{(srfi :134)}.

    The name @code{texts} is taken from sample implementation.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-139/srfi-139.html"]{SRFI-139}}
    @td{(srfi :139 syntax-parameters)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :139)}. So for the portability it's better to use the
    @code{(srfi :139)}.

    The name @code{syntax-parameters} is taken from sample implementation.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-141/srfi-141.html"]{SRFI-141}}
    @td{(srfi :141 integer-division)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-142/srfi-142.html"]{SRFI-142}}
    @td{(srfi :142 bitwise)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :142)}. So for the portability it's better to use the
    @code{(srfi :142)}.

    The name @code{bitwise} is taken from the name of the SRFI.

    This SRFI is deprecated by SRFI-151.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-143/srfi-143.html"]{SRFI-143}}
    @td{(srfi :143 fixnums)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-144/srfi-144.html"]{SRFI-144}}
    @td{(srfi :144 flonums)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :144)}. So for the portability it's better to use the
    @code{(srfi :144)}.

    The name @code{flonums} is taken from the name of the SRFI.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-145/srfi-145.html"]{SRFI-145}}
    @td{(srfi :145 assumptions)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-146/srfi-146.html"]{SRFI-146}}
    @td{(srfi :146 mapping) and (srfi :146 hash)

    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :146)} and @code{(srfi :146 hash)}. So for the portability it's better to use them.

    The name @code{mapping} is taken from the name of the SRFI.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-151/srfi-151.html"]{SRFI-151}}
    @td{(srfi :151 bitwise-operations)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-152/srfi-152.html"]{SRFI-152}}
    @td{(srfi :152 strings)
    This library doesn't extend comparisons, thus it behaves as the SRFI specifies.
    (e.g. Passing 0 or 1 argument to @code{string=?} raises an error)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-154/srfi-154.html"]{SRFI-154}}
    @td{(srfi :154 dynamic-extents)
    The long name is Sagittarius specific and the specified library name 
    is @code{(srfi :154)}. So for the portability it's better to use them.

    The name @code{dynamic-extents} is taken from the name of the SRFI.
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-156/srfi-156.html"]{SRFI-156}}
    @td{(srfi :156 predicate-combiners)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-158/srfi-158.html"]{SRFI-158}}
    @td{(srfi :158 generators-and-accumulators)
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-159/srfi-159.html"]{SRFI-159}}
    @td{(srfi :159)}}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-160/srfi-160.html"]{SRFI-160}}
    @td{(srfi :160)

    The short name is Sagittarius specific which provides all the bindings
    from the below libraries which are specified in the SRFI:
    @itemlist{
    @item{(srfi :160 base)}
    @item{(srfi :160 u8)}
    @item{(srfi :160 s8)}
    @item{(srfi :160 u16)}
    @item{(srfi :160 s16)}
    @item{(srfi :160 u32)}
    @item{(srfi :160 s32)}
    @item{(srfi :160 u64)}
    @item{(srfi :160 s64)}
    @item{(srfi :160 f32)}
    @item{(srfi :160 f64)}
    @item{(srfi :160 c64)}
    @item{(srfi :160 c128)}
    }
    }}
@tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-197/srfi-197.html"]{SRFI-197}}
    @td{(srfi :197 pipeline)

        The long name is Sagittarius specific and the specified library name 
	is @code{(srfi :197)}. So for the portability it's better to use the
    	@code{(srfi :197)}.
    }}
@; > In order to facilitate writing sophisticated custom macro transformers, it
@; > is allowed that a transformer spec expands into a sequence of multiple
@; > definitions eventually followed by a transformer spec (whose expansion may
@; > make use of the introduced definitions).
@; Above sentence makes this srfi more trouble than gain so don't dare.
@;
@; @tr{@td[:style "vertical-align: top;"]{@hyperlink[:href "http://srfi.schemers.org/srfi-147/srfi-147.html"]{SRFI-147}}
@;     @td{(srfi :147 custom-macro-transformers)
@; 
@;     The long name is Sagittarius specific and the specified library name 
@;     is @code{(srfi :147)}. So for the portability it's better to use the
@;     @code{(srfi :147)}.
@; 
@;     The name @code{custom-macro-transformers} is taken from the name of the
@;     SRFI.
@;     }}
}


Each library can be imported like this: 
@snipet{(import (srfi :1))}
So you don't have to type the long name.

All libraries have R7RS style library name as well. So SRFI-1 can be imported
like this:
@snipet{(import (srfi 1))}

@subsection[:tag "srfi.reader.macro"]{Reader macros for SRFIs}

@subsubsection{SRFI-4}

The SRFI-4 also defines its reader macro. Sagittarius also suppots these. It
defines tagged vector and the tags can be @code{s8}, @code{u8}, @code{s16},
@code{u16}, @code{s32}, @code{u32}, @code{s64}, @code{u64}, @code{f32} or
@code{f64}. For each value of tags, the external representation of instances of
the vector is @code{#@var{tag}(... elements ...)}

On Sagittarius, these reader macros are not automatically enabled. You need to
explicitly import it. For more detail, see
@secref["lib.sagittarius.reader"]{(sagittarius reader) - reader macro library}.

