StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11696822
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-27T23:19:46.060
FavoriteCount
0
LastActivityDate
2012-07-27T23:44:07.817
LastEditDate
2012-07-27T23:44:07.817
LastEditorUserId
87234
OwnerUserId
87234
ParentId
11696739
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
It looks like it's just an oversight in the standard specification. <code>ios_base::precision</code> has two overloads, one that gets and one that sets the precision: <pre><code>// returns current precision streamsize precision() const; // sets current precision and returns old value streamsize precision(streamsize prec) const; </code></pre> So this code will not give you warnings: <pre><code>#include <iostream> int main() { std::streamsize prec = std::cout.precision(); // gets std::cout.precision(prec); // sets } </code></pre> However, the <code>setprecision()</code> function simply takes a plain old <code>int</code>: <pre><code>unspecified-type setprecision(int n); </code></pre> and returns an unspecified functor, which when consumed by a stream <code>str</code> has the effect of: <pre><code>str.precision(n); </code></pre> In your case, <code>streamsize</code> is not an <code>int</code> (and does not have to be), hence the warning. The standard should probably be changed so that <code>setprecision</code>'s parameter is not <code>int</code>, but <code>streamsize</code>. You can either just call <code>precison()</code> yourself, as above, or assume <code>int</code> is sufficient and cast. <pre><code>#include <iomanip> #include <iostream> int main() { std::streamsize prec = std::cout.precision(); std::cout << std::setprecision(static_cast<int>(prec)); } </code></pre> Edit: <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-closed.html#1148" rel="nofollow">Apparently it was submitted to be fixed and reached no concensus (closed as not-a-defect)</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy compiler warns about implicit conversion in setprecision?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGManNickG
UserOwnerUserId
1. USGManNickG
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy compiler warns about implicit conversion in setprecision?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.