The Khronos reference page contains description of parameters and description of the behavior for every function. Wouldn't it be possible to add doc comments for the functions, so IDE can show it? I understand the function description is a bit cumbersome, as one description is usually related to multiple functions with similar functionality, however parameters description would help a lot.
I am c

I'm using tsv-utils from the arch linux aur, trying to format some word frequency data from the new general services list dataset. tsv-utils makes at least two errors that I'm able to see when I'm running this commandline:

tsv-select -f 1,7 NGSL+1.01+with+SFI.tsv | tsv-pretty | less

adding -s 5 to tsv-pretty works around this problem. The tsv file was converted from the file NGSL+1.01+with

Example:

• https://github.com/vibe-d/vibe.d/blob/3d0558e286ef89232e277c24332d12c30de02af0/http/vibe/http/client.d#L386
• https://github.com/vibe-d/vibe.d/blob/3d0558e286ef89232e277c24332d12c30de02af0/http/vibe/http/server.d#L706-L707
• https://github.com/vibe-d/vibe.d/blob/3d0558e286ef89232e277c24332d12c30de02af0/mongodb/vibe/db/mongo/connection.d#L204

And this is broken:

• https://github.c

LLVM will soon support adding per-function attributes about available C library functions. We should add support for that, to solve issues like a memcpy implementation being replaced by a memcpy call: https://forum.dlang.org/thread/clptjumxigcozfcyhzzx@forum.dlang.org
Probably ldc.attributes.llvmAttrwill already work for this, but I think it'd be nice to have a more userfriendly attribute.
Som

Github Markdown lets you do language highlighting in your readmes and on the wiki. If the wiki is open to edit, I'll go add that support now, but seeing the readme with good highlighting would be good too, both D and sh.
Put the name of the language after the first set of triple backtics.

E.g. dub add-path "C:\Dev\" from cmd.exe leads to an entry in local-packages.json like this:

	{
		"name": "*",
		"path": "C:\\Dev\""
	},

note the trailing single \ and extra "

I'm using a build from current master on OSX Sierra. When I drag the window to my second monitor the text gets insanely large. I'm moving the window from retina display on a MacBookPro to a 1080p monitor:

Is your feature request related to a problem? Please describe.
Yes. GUI is for children and CLI doesn't give me the launching capabilities.

Describe the solution you'd like
A non-gui/non-cli frontend

Describe alternatives you've considered
Ncurses

Additional context
None

The examples don't run on Travis right now because they fail - the older version of libclang there, even when installing the most recent one from apt, doesn't work the same way as libclang 6.0. The CI script should manually download the right libclang version, just like dstep does.

probably not a good user experience to get the undocumented/const checks by default

unused is shown as grayed out right now already

Transferred from: https://issues.dlang.org/show_bug.cgi?id=18401

User @wilzbach reported (2018-02-08 21:05:07 CET):

These pages have a tendency to get outdated:

• https://github.com/dlang/tools/blob/master/man/man1/rdmd.1
• https://dlang.org/rdmd.html

We should generate them like we do for dmd. They are even outdated atm - search for --shebang on the man page.

Browsing docs in ./doc is awful - no navigation, no table of contents, etc. Maybe it's better to host docs on the GitHub wiki, https://readthedocs.org/ or somewhere else?

Please consider a brief document with simple instructions leading from zero to a simple 'hello world' style app.
Show minimal code (in full context) to build a working/useful starting point to hack outwards from.
Ideally, there would be a couple of such snippets showing incremental addition of APIs.

According to the SFML 2.4 documentation, the TcpSocket class should have a send method for raw data that returns the number of bytes sent as an out parameter.

In non-blocking mode, it may not be the case that a TcpSocket sent everything, which a developer would need to know.