* Proposal: GSOC 2015 project -- Rewrite the Pandoc Markdown Parser
@ 2015-03-26 16:39 Vincent Zhao
0 siblings, 0 replies; only message in thread
From: Vincent Zhao @ 2015-03-26 16:39 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
[-- Attachment #1.1: Type: text/plain, Size: 2443 bytes --]
Hi my name is Vincent and I'm from Peking University, China. It's my third
year of studying computer science. Basically my research projects are
related to high performance computing, I've got a CGO2015 submission last
summer(if you're interested: Optimizing and auto-tuning scale-free sparse
matrix-vector multiplication on Intel Xeon Phi
<https://scholar.google.com/citations?view_op=view_citation&hl=en&user=RX1JK2IAAAAJ&citation_for_view=RX1JK2IAAAAJ:u5HHmVD_uO8C>).
Besides this, I'm really into Haskell, both its theory and practice. Pandoc
is the best application in Haskell that I've ever seen.
So I really want to contribute in this project: Rewrite the Pandoc Markdown
Parser <https://ghc.haskell.org/trac/summer-of-code/ticket/1660>.
It seems that you're arguing that Pandoc too large to serve some slim
applications(Proposal: Alternate Granular Package Organization
<https://groups.google.com/forum/#!topic/pandoc-discuss/RqX0GkpqH04>), for
example, a simple Markdown parser which could conform CommonMark standard.
And I think that might what I could do.
Here're the formal content:
1. I'll read through the core part of Pandoc, including the Parser
libraries. After reading that, I'll try to extract lines that a CommonMark
parser should need. If the size is still large, I may rewrite a small
Parser for that standard(Basically I know how to use Parsec, and that might
be the way I should choose).
2. After a small workable application finished, I'll work on enhancing its
performance, as it is said that Parsec could only achieve 1/3 of JS version
performance. Then, try to optimize this small set of Pandoc.
3. Extra: If time permits, I could help building a framework for small
extensions just like the CommonMark parser I'll build. But I think this one
needs all of us to discuss.
Hope to hear from you guys!
Thanks,
Vincent
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/fc76ee32-ba45-4c66-931e-6429874fef0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 4008 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-03-26 16:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-26 16:39 Proposal: GSOC 2015 project -- Rewrite the Pandoc Markdown Parser Vincent Zhao
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).