Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>C++ isn't meant to support laziness. Using lambdas instead of normal functions is no exception here.</p> <p>This</p> <pre><code>int f(vector&lt;int&gt; v) { sort(begin(v), end(v)); v.erase(unique(begin(v), end(v)), end(v)); copy(begin(v), end(v), ostream_iterator&lt;int&gt;(cout, " ")); cout &lt;&lt; endl; /* And then the function uses these helpers a few more times to justify making functions... */ } </code></pre> <p><strong>is much more succinct, standard, and readable</strong> than this</p> <pre><code>int f(vector&lt;int&gt; v) { auto make_unique = [](vector&lt;int&gt; &amp;v) { sort(begin(v), end(v)); auto unique_end = unique(begin(v), end(v)); v.erase(unique_end, end(v)); }; auto print_vector = [](vector&lt;int&gt; const &amp;v) { copy(begin(v), end(v), ostream_iterator&lt;int&gt;(cout, " ")); cout &lt;&lt; endl; }; make_unique (v); print_vector(v); /* And then the function uses these helpers a few more times to justify making functions... */ } </code></pre> <p>As a general rule of thumb, when your code itself isn't obscure (<code>erase</code> and <code>sort</code> and <code>copy</code> aren't obscure, they're standard C++ algorithms), adding more code only makes it worse.</p> <p>Furthermore: there is no reason to restrict the type of <code>v</code> to <code>vector&lt;int&gt;</code> in so many places.<br> Use type inference wherever the type doesn't matter.</p> <p>If you feel it should be a separate function, then make it a separate function entirely.<br> Don't use lambdas as a crutch for being lazy.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs it good style to use lambda functions to define very small helper functions?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMehrdad
    1. USMehrdad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI agree with most of your answer, but how is using a lambda being lazy? Also isn't being lazy at the heart of programming, do less typing get more work done, write code as simply as possible
      singulars
      1. PO
      1. USaaronman
    2. CO@aaronman: It's being lazy because it's screaming "I think this should be a separate function or functor, but I don't feel like actually making it one so I'll just leave it as a lambda around here". If it shouldn't be a function then it shouldn't be a lambda either. If it should be a function then it should be a function. Lambdas aren't meant for organizing code, they're meant for supporting functional programming (i.e. being passed to other functions).
      singulars
      1. PO
      1. USMehrdad
    3. COTotally agree, with everything, except to me making a function makes my life way easier and is therefore lazy
      singulars
      1. PO
      1. USaaronman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload