Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IntStr, NumStr, RatStr and ComplexStr not documented #418

Closed
4 tasks done
AlexDaniel opened this issue Mar 9, 2016 · 6 comments
Closed
4 tasks done

IntStr, NumStr, RatStr and ComplexStr not documented #418

AlexDaniel opened this issue Mar 9, 2016 · 6 comments
Assignees
@jonathanstowe
Labels
docs Documentation issue (primary issue type)

Comments

@AlexDaniel
Copy link
Member

AlexDaniel commented Mar 9, 2016 •
edited by Timbus

  • IntStr
  • NumStr
  • RatStr
  • ComplexStr

Feel free to submit a separate commit for each
@AlexDaniel AlexDaniel added the docs Documentation issue (primary issue type) label Mar 24, 2016
@AlexDaniel AlexDaniel mentioned this issue May 24, 2016
Closed
@jonathanstowe
Copy link
Contributor

Infact all of the "allomorphs" should be documented, that is IntStr, NumStr, RatStr and ComplexStr ...

@AlexDaniel AlexDaniel changed the title IntStr is not documented IntStr, NumStr, RatStr and ComplexStr not documented May 24, 2016
@AlexDaniel
Copy link
Member Author

@jonathanstowe good catch! I've changed the title.

@jonathanstowe jonathanstowe self-assigned this May 24, 2016
@jonathanstowe
Copy link
Contributor

Just picking this up.

jonathanstowe added a commit that referenced this issue May 24, 2016
@jonathanstowe
Add doc pages for "allomorphs"
b02c2f0 
Covers #418
jonathanstowe added a commit that referenced this issue May 24, 2016
@jonathanstowe
Document the val() from allomorphs.pm
819be1a 
Covers #418
jonathanstowe added a commit that referenced this issue May 24, 2016
@jonathanstowe
add allomorph to glossary
5f2684c 
covers #418
@jonathanstowe
Copy link
Contributor

Some of this stuff may want linking from the quoting and wherever MAIN is documented, but this should cover it off for the most part.

@AlexDaniel
Copy link
Member Author

@jonathanstowe do you think that it requires more work under this ticket? It looks closeable to me.

@jonathanstowe
Copy link
Contributor

I think it's done yeah :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonathanstowe jonathanstowe

Labels
docs Documentation issue (primary issue type)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonathanstowe @AlexDaniel