about summary refs log tree commit diff
path: root/src/rustllvm/ExecutionEngineWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2014-08-11 03:36:11 +0000
committerbors <bors@rust-lang.org>2014-08-11 03:36:11 +0000
commit4d27b4875e16ed6a4a0c9697432f1152b727e84a (patch)
tree14156aecfe8b49626fe840d0ed5c57055e07351c /src/rustllvm/ExecutionEngineWrapper.cpp
parentc4a63fabe345967e7d6b4570752ea081cae21785 (diff)
parent14e245bd47d3ac1a981d50a6f752aa27cca7d85e (diff)
downloadrust-4d27b4875e16ed6a4a0c9697432f1152b727e84a.tar.gz
rust-4d27b4875e16ed6a4a0c9697432f1152b727e84a.zip
auto merge of #15410 : LemmingAvalanche/rust/patch-1, r=alexcrichton
People reading the tutorial may not be familiar with the convention of naming lists, vectors and the like as xs, ys, etc. Without some explanation of the reasoning behind it, it might come off as just throwaway non-descriptive names. Languages like Haskell gets flak from using short, non-descriptive names, while in reality, there are clear conventions and reasons for using certain terse variable names. 

This is just a proposed explanation of this convention, as I've interpreted it - I assumed that the convention came from a language like Haskell, so I tailored it according to that. So beware that I might have misjudged how it is used in the Rust language, or at least how it is used in the Rust tutorial.
Diffstat (limited to 'src/rustllvm/ExecutionEngineWrapper.cpp')
0 files changed, 0 insertions, 0 deletions