You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The interface-reference report has some problems determining the correct library and module names. I ran the report for the collection-extensions library and it has two problems I've noticed so far:
Classes in the Dylan library are output as :class:<foo> rather than :drm:<foo> even though the report attempts to do the latter, so there's a bug in the logic of rst-xref-definition-name where it compares the library name to "dylan". (In that function lib has to be true, else we would see the problem below...
The type <insert-entry> is output as follows
``{<insert-entry> in sequence-diff}``
Since sequence-diff is the current module for this output it should just be
:class:`<insert-entry>`
The text was updated successfully, but these errors were encountered:
It generates an entry for names that are re-exported from the module, but there's no indication that they are in fact defined elsewhere and just re-exported. For example, the report for common-dylan contains
.. generic-function:: ^:open::signature: ^ (x y) => (#rest values)
:parameter x: An instance of :class:`<object>`.
:parameter y: An instance of :class:`<object>`.
:value #rest values: An instance of :class:`<object>`.
The
interface-reference
report has some problems determining the correct library and module names. I ran the report for thecollection-extensions
library and it has two problems I've noticed so far:Classes in the Dylan library are output as
:class:<foo>
rather than:drm:<foo>
even though the report attempts to do the latter, so there's a bug in the logic ofrst-xref-definition-name
where it compares the library name to "dylan". (In that functionlib
has to be true, else we would see the problem below...The type
<insert-entry>
is output as followsSince sequence-diff is the current module for this output it should just be
The text was updated successfully, but these errors were encountered: