search for: _fmt

...yntax. So you can look at this without looking at the code behind it and see if you have comments just on the format language. Here's a summary of (most) everything contained in this patch: 1) UDL Syntax for outputting to a stream or converting to a string. outs() << "{0}"_fmt.stream(1) std::string S = "{0}"_fmt.string(1); 2) Built-in format providers for various common types: outs() << "{0}"_fmt.stream("test"); // "test" outs() << "{0}"_fmt.stream(StringRef("test")); // &...

On 12.10.2016 05:59, Mehdi Amini via llvm-dev wrote: >> If you change a const char * to a StringRef, it can silently succeed >> while passing your StringRef object to printf. It should fail to compile! > > llvm::format now fails to compile as well :) > > However this does not address other issues, like: `format(“%d”, float_var)` This may be a good time to point at

...gt; without looking at the code behind it and see if you have comments just on > the format language. > > Here's a summary of (most) everything contained in this patch: > > 1) UDL Syntax for outputting to a stream or converting to a string. > outs() << "{0}"_fmt.stream(1) > std::string S = "{0}"_fmt.string(1); > I continue to have a strong objection to using UDLs for this (or anything else in LLVM). I think this feature is poorly known by many programmers. I think it will produce error messages that are confusing and hard to debug. I...

...he code behind it and see if you have comments just on >> the format language. >> >> Here's a summary of (most) everything contained in this patch: >> >> 1) UDL Syntax for outputting to a stream or converting to a string. >> outs() << "{0}"_fmt.stream(1) >> std::string S = "{0}"_fmt.string(1); >> > > I continue to have a strong objection to using UDLs for this (or anything > else in LLVM). > > I think this feature is poorly known by many programmers. I think it will > produce error messages that...

...gt; without looking at the code behind it and see if you have comments just on > the format language. > > Here's a summary of (most) everything contained in this patch: > > 1) UDL Syntax for outputting to a stream or converting to a string. > outs() << "{0}"_fmt.stream(1) > std::string S = "{0}"_fmt.string(1); > > > I continue to have a strong objection to using UDLs for this (or anything > else in LLVM). > > I think this feature is poorly known by many programmers. I think it will > produce error messages that are con...

...gt; without looking at the code behind it and see if you have comments just on > the format language. > > Here's a summary of (most) everything contained in this patch: > > 1) UDL Syntax for outputting to a stream or converting to a string. > outs() << "{0}"_fmt.stream(1) > std::string S = "{0}"_fmt.string(1); > > > I continue to have a strong objection to using UDLs for this (or anything > else in LLVM). > > I think this feature is poorly known by many programmers. I think it will > produce error messages that are con...

This probably qualifies as bikeshedding, but how strict are the style norms for TableGen? Some aspects of it, like individually and consecutively declaring all *_ENC variables in this manner: class ADDU_QB_ENC : ADDU_QB_FMT<0b00000>; To be used only once, in this manner: def ADDU_QB : ADDU_QB_ENC, ADDU_QB_DESC; Seem like avoidable clutter to me. The files tend to be pretty big, and I think that collapsing assignments like that could make them more readable. I'm new to this, so let me know if I'm...

This patch series introduces the tapback daemon, the user space daemon that acts as a device''s back-end, essentially most of blkback in user space. The daemon is responsible for coordinating the front-end and tapdisk. It creates tapdisk process as needed, instructs them to connect to/disconnect from the shared ring, and manages the state of the back-end. The shared ring between the

...magine wanting to write a function like > printRange(const char *Fmt, std::vector<int> Items); > > > I’m not sure I understand your example? > Do you mean you want the range to be in the format? If so Why? I would > rather write something like: > > printRange(“{per_elts_fmt}”, /* separator */ “, ", begin, end); > > This isn't possible if your format string MUST be a string literal > > > I haven’t seen a convincing example yet to support this. I may miss the > obvious, but you haven’t shown it either. > One could find a way to *compose* fo...

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>