Replies: 2 comments
-
|
Actually it seems to work correctly for other ones such as the term api. So there seems to be some inconsistency there. Maybe only the global functions are affected? Can't verify right now. On that topic though: The source for the terminal api actually isn't very helpful either because it links to the abstract class, not the actual implementation. I want to see the code that gets executed when I run "term.write()" in a computer, not the abstract wrapper that calls "term.write()" on some uninitialized terminal. |
Beta Was this translation helpful? Give feedback.
-
|
It is a limitation of the doc generator CC:T is using I think. Since the Anyway I don't think it's necessary to look at the source of |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Pretty much the title, didn't want to open another issue that turns out to be with me and not the project.
For example, I tried looking at the documentation for print to see whether it yields, didn't find the answer, so I wanted to look at the source code instead to figure it out. But clicking on the "[Source]" button redirects to the implementation of the documentation not the implementation of print. Is that intended?
This has actually been bothering me for years, but only now did the realization hit me that this is probably a bug that needs fixing.
Beta Was this translation helpful? Give feedback.
All reactions