-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
Add papers. #110
base: master
Are you sure you want to change the base?
Add papers. #110
Conversation
booktitle = {DLS} | ||
} | ||
|
||
@inproceedings{bolz07not, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could not find booktitle
for this one...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"3rd Workshop on Dynamic Languages and Applications" according to https://scholar.google.com/citations?view_op=view_citation&hl=en&user=S0rpYpkAAAAJ&citation_for_view=S0rpYpkAAAAJ:8k81kl-MbHgC
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I thought we keep booktitle
for events/conferences.
Are journals basically the same thing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From memory, we use 'booktitle' to mean "event" (you can look elsewhere in the file for precedent).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated 👉 36f4a35
@@ -3335,19 +3335,36 @@ @article{yanovski21ghostcell | |||
} | |||
|
|||
@inproceedings{cheng20typefreezing, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one and the next seem to just be changing whitespace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes I re-formatted it to have the same indentation :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future, I don't mind that being in another commit, but the problem with whitespace changes is that they detract from the more important bits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
got it.
Please squash. |
fc8f306
to
d7d2c03
Compare
Squashed 👉 d7d2c03 |
} | ||
|
||
@inproceedings{ancona07rpython, | ||
title = {RPython: a step towards reconciling dynamically and statically typed OO languages}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just spotted: you'll need to add curly brackets around "RPython" and "OO".
Added more papers.
Not sure if all of them are relevant for general use :)