Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On Tuesday, 5 May 2020 at 21:41:39 UTC, Dmitry Olshansky wrote: On Tuesday, 5 May 2020 at 20:11:44 UTC, Robert M. Münch wrote: On 2020-05-05 15:39:12 +, Dmitry Olshansky said: On the other hand, if you can help someone to get started and it's a couple of hours, I would expect people to be fair enough and state: Hey, $400 (or whatever) is OK, let's take the rest to sponsor something else. That's what I would do. So here goes, indeed about 4.5 hours so far. The generator is untangled from the old crap from that GSOC 2012 repo: https://github.com/DmitryOlshansky/gen-uni-dlang PR: https://github.com/dlang/phobos/pull/7469 Let's see if the CI loves it or not.
Re: D IDE Dexed - v3.9.0
On Tuesday, 5 May 2020 at 20:05:25 UTC, notna wrote: On Tuesday, 5 May 2020 at 20:03:38 UTC, notna wrote: On Tuesday, 5 May 2020 at 12:53:29 UTC, Basile B. wrote: On Win10 64Bit, after compiling as described in https://basile.b.gitlab.io/dexed/build.html, I have a "dexed.exe" but if I run it, I get "couldn't find dexed-d.dll" ... Can you give a try again after pulling latest changes ? Actually the library indicated as missing was build by calling bash which obviously could not work on Windows. I have pushed a change that replaces this by a direct call to dub since the script was essentially used to "cd" and that's not required as dub has "--root" Thanks for your changes. Seems like linking take a bit longer now but the DLL is still not build. The log from DUB tends to say the opposite. The dll should be in "C:\Temp\Git\dexed\bin". Maybe the extension is missing then ? Another change => calling "dexed.exe" doesn't shop the error popup as it did before... grrr... doesn't _SHOW_ the error popup as it did before... Try the default procedure now. i.e using lazbuild as explained in the documentation. As the library is statically linked this is mandatory anyway.
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On Tuesday, 5 May 2020 at 20:11:44 UTC, Robert M. Münch wrote: On 2020-05-05 15:39:12 +, Dmitry Olshansky said: On Monday, 4 May 2020 at 17:01:01 UTC, Robert M. Münch wrote: Following my "Is it time for a Unicode update of std.uni?" post in D group, I would like to try out to sponsor this effort for "Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)" [1] For me, this, too, is an experiment to find out if it's possible to move specific issues/topics forward. And maybe even find people that are open to contact work too. For me, all these things are pretty related. So, not knowing how much work it is, nor knowing what a good amount would be, I took the other route and asked me, what is it worth for me to get it done? Note: Getting #16416 done is not critical for me; most likely, I could even live with the current state of std.uni. On the other hand, std.uni is a very fundamental building block, and having it up to date and maybe even extended should be much value to D. So, I'm offering $750 to get it done. I'm guess I'm not eligible for the bounty ;) Why not? Felt a bit like cheating. Russian traditions preclude taking money for things you (think you) wanted to do anyway. Anyhow if anyone wants easy money - shoot me an email, or reply in this thread. Well, as I wrote, since I don't have a real good understanding about the necessary effort I started from "what is it worth for me in $ to get it done?". So, if it's a simple script-change and a re-run and you are the only one knowing this and keeping it for yourself... yes, it's easy money. On the other hand, if you can help someone to get started and it's a couple of hours, I would expect people to be fair enough and state: Hey, $400 (or whatever) is OK, let's take the rest to sponsor something else. That's what I would do. I started on it, and it turned out a bit more then I hope for + I'm doing it on simple Windows workstation without much of my usual power tools. LDC for Windows works like a charm though. It seems Unicode 13.0.0 pulled a plug on a couple of "derived" tables, that is data files that can be reconsturcted from other primary ones. Took at least half an hour to figure that out and rebuild the missing bits. If you don't mind I'll go with 100$ per hour estimate which is basically my usual contract rate. It took me about 2 hours for now, and I think I'd be done in a one or two more. Merging this into Phobos though is the otehr 90% of the legwork, I hope somebody will help me with that and maybe we'll just split your generous bounty this way. Spoiler is - the whole thing is code generated and there is only one table that I forgot about (i.e. I have no idea what is the source table for it in Unicode standard). With "forgot" you mean, you can't remember, or it's missing at all in your prior work? I mean I know what this table does by its usage but the codegen part is missing, likely a classic missing commit problem of being a single maintainer of the codegen tool (and the fact that it's not in the main dlang repos). P.S. I'm kind of back, but very busy and my health is mostly great despite the COVID outrage out there. That's great to hear... and maybe std.uni support/coaching for someone stepping up is possible. That would be great too. If, maybe even I can try to do it... Absolutely. I mean I'm in no shape to do the heavy lifting of day in day out maintanance of std.* stuff but I'd love to coach somebody to learn how std.regex and std.uni work. I can also share my vision for improvement, and will gladly help with refactoring. Both of modules predate many of the good things in DLang and std.allocator in particular. Boy, I'd love to have allocators back in the day. -- Dmitry Olshansky
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On 2020-05-05 15:39:12 +, Dmitry Olshansky said: On Monday, 4 May 2020 at 17:01:01 UTC, Robert M. Münch wrote: Following my "Is it time for a Unicode update of std.uni?" post in D group, I would like to try out to sponsor this effort for "Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)" [1] For me, this, too, is an experiment to find out if it's possible to move specific issues/topics forward. And maybe even find people that are open to contact work too. For me, all these things are pretty related. So, not knowing how much work it is, nor knowing what a good amount would be, I took the other route and asked me, what is it worth for me to get it done? Note: Getting #16416 done is not critical for me; most likely, I could even live with the current state of std.uni. On the other hand, std.uni is a very fundamental building block, and having it up to date and maybe even extended should be much value to D. So, I'm offering $750 to get it done. I'm guess I'm not eligible for the bounty ;) Why not? Anyhow if anyone wants easy money - shoot me an email, or reply in this thread. Well, as I wrote, since I don't have a real good understanding about the necessary effort I started from "what is it worth for me in $ to get it done?". So, if it's a simple script-change and a re-run and you are the only one knowing this and keeping it for yourself... yes, it's easy money. On the other hand, if you can help someone to get started and it's a couple of hours, I would expect people to be fair enough and state: Hey, $400 (or whatever) is OK, let's take the rest to sponsor something else. That's what I would do. Spoiler is - the whole thing is code generated and there is only one table that I forgot about (i.e. I have no idea what is the source table for it in Unicode standard). With "forgot" you mean, you can't remember, or it's missing at all in your prior work? P.S. I'm kind of back, but very busy and my health is mostly great despite the COVID outrage out there. That's great to hear... and maybe std.uni support/coaching for someone stepping up is possible. That would be great too. If, maybe even I can try to do it... -- Robert M. Münch http://www.saphirion.com smarter | better | faster
Re: D IDE Dexed - v3.9.0
On Tuesday, 5 May 2020 at 20:03:38 UTC, notna wrote: On Tuesday, 5 May 2020 at 12:53:29 UTC, Basile B. wrote: On Win10 64Bit, after compiling as described in https://basile.b.gitlab.io/dexed/build.html, I have a "dexed.exe" but if I run it, I get "couldn't find dexed-d.dll" ... Can you give a try again after pulling latest changes ? Actually the library indicated as missing was build by calling bash which obviously could not work on Windows. I have pushed a change that replaces this by a direct call to dub since the script was essentially used to "cd" and that's not required as dub has "--root" Thanks for your changes. Seems like linking take a bit longer now but the DLL is still not build. Another change => calling "dexed.exe" doesn't shop the error popup as it did before... grrr... doesn't _SHOW_ the error popup as it did before...
Re: D IDE Dexed - v3.9.0
On Tuesday, 5 May 2020 at 12:53:29 UTC, Basile B. wrote: On Win10 64Bit, after compiling as described in https://basile.b.gitlab.io/dexed/build.html, I have a "dexed.exe" but if I run it, I get "couldn't find dexed-d.dll" ... Can you give a try again after pulling latest changes ? Actually the library indicated as missing was build by calling bash which obviously could not work on Windows. I have pushed a change that replaces this by a direct call to dub since the script was essentially used to "cd" and that's not required as dub has "--root" Thanks for your changes. Seems like linking take a bit longer now but the DLL is still not build. Another change => calling "dexed.exe" doesn't shop the error popup as it did before... ```powershell C:\Temp\Git\dexed\dexed-d [master ≡] λ dub.exe --compiler=ldc2 Performing "debug" build using ldc2 for x86_64. iz ~master: building configuration "library"... stdx-allocator 2.77.5: building configuration "library"... libdparse ~master: building configuration "library"... dexed-d ~master: building configuration "library"... Linking... Target is a library. Skipping execution. C:\Temp\Git\dexed\dexed-d [master ≡] λ ls Directory: C:\Temp\Git\dexed\dexed-d ModeLastWriteTime Length Name - -- d- 05.05.2020 21:57.dub d- 03.05.2020 14:40src -a 03.05.2020 14:40307 dub.json -a 05.05.2020 21:48144 dub.selections.json C:\Temp\Git\dexed\dexed-d [master ≡] λ ls .\src\ Directory: C:\Temp\Git\dexed\dexed-d\src ModeLastWriteTime Length Name - -- -a 03.05.2020 14:40 9863 common.d -a 03.05.2020 14:40897 ddemangle.d -a 03.05.2020 14:40 6436 ddoc_template.d -a 03.05.2020 14:40 27235 halstead.d -a 03.05.2020 14:40 4321 imports.d -a 03.05.2020 14:40 1663 mainfun.d -a 03.05.2020 14:40 12663 symlist.d -a 03.05.2020 14:40 3397 todos.d C:\Temp\Git\dexed\dexed-d [master ≡] λ cd .. C:\Temp\Git\dexed [master ≡] λ fd --glob *.dll C:\Temp\Git\dexed [master ≡] ```
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On Monday, 4 May 2020 at 17:01:01 UTC, Robert M. Münch wrote: ... I believe this is an excellent initiative, thank you for starting it! Perhaps this script, along with repository that is part of can help those wishing to update std.uni to the latest version: https://github.com/DmitryOlshansky/gsoc-bench-2012/blob/master/gen_uni.d With regard to the rate of pull requests being merged into the core repositories, I would say that it is highly contextually dependent. I strongly advise either: a) subscribing for notifications from the core dlang repositories (dmd, druntime, phobos, dub, etc.) for an extended period of time (3 months min) - you'll be able to observe the group dynamics (e.g. which contributors have experience with which part of the codebase, why some things are merged quickly and others take a while, etc.) - this way you can really draw conclusions for yourself (b) looking at the statistics: - https://github.com/dlang/dmd/pulse/monthly - https://github.com/dlang/druntime/pulse/monthly - https://github.com/dlang/phobos/pulse/monthly - https://github.com/dlang/dub/pulse/monthly as opposed to drawing conclusions from single data points of anecdotal evidence. From my several years of experience, I can say the following: - small, less complex pull requests are generally easy to get merged - it depends on the part of the codebase - if you open a pull request for a part whose maintainers are currently active, you can expect a speedy review. If it's a part (e.g. std.regex) that is both highly complex and with a small number of maintainers, then it may take a while) - teamwork and communication - since all of us are living in different time zones, rather than working in the same office, you should be prepared that communication (which is a prerequisite of merging) will be with high-latency. Changes that are described well, for which the benefit is clear and doesn't look like they may introduce regressions are of course received well. Discussion prior to opening a merge request can help to guide the implementation in the right direction and save time later in the review process. Many contributors are active on the dlang Slack [1] which makes it a good place to ping people for feedback, or just to have a near real-time conversation. In the past 1-3 years, I have noticed a trend that many active contributors are mostly active on GitHub and Slack, rather than the newsgroup. If you see that pull request has fallen through the cracks (no new replies from maintainers), don't hesitate to ping us either there or here on the newsgroup. [1]: https://dlang.slack.com/
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On 05.05.20 17:39, Dmitry Olshansky wrote: I'm guess I'm not eligible for the bounty ;) Why wouldn't you be eligible? If it's an easy fix for you, that's just because you've got the needed expert knowledge. And that's valuable.
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On Monday, 4 May 2020 at 17:01:01 UTC, Robert M. Münch wrote: Following my "Is it time for a Unicode update of std.uni?" post in D group, I would like to try out to sponsor this effort for "Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)" [1] For me, this, too, is an experiment to find out if it's possible to move specific issues/topics forward. And maybe even find people that are open to contact work too. For me, all these things are pretty related. So, not knowing how much work it is, nor knowing what a good amount would be, I took the other route and asked me, what is it worth for me to get it done? Note: Getting #16416 done is not critical for me; most likely, I could even live with the current state of std.uni. On the other hand, std.uni is a very fundamental building block, and having it up to date and maybe even extended should be much value to D. So, I'm offering $750 to get it done. I'm guess I'm not eligible for the bounty ;) Besides getting the work done, there is one constraint: The work needs to get into Phobos. It doesn't make sense to have it sit around, because it's not being merged. I don't have any clue who is in charge, who decides this. Or if there need to be some conditions full-filled so that the result gets merged. Anyhow if anyone wants easy money - shoot me an email, or reply in this thread. Spoiler is - the whole thing is code generated and there is only one table that I forgot about (i.e. I have no idea what is the source table for it in Unicode standard). [1] https://issues.dlang.org/show_bug.cgi?id=16416 P.S. I'm kind of back, but very busy and my health is mostly great despite the COVID outrage out there. --- Dmitry Olshansky
Re: Luneta: terminal fuzzy finder
On Tuesday, 5 May 2020 at 06:48:41 UTC, Fynn Schröder wrote: On Monday, 4 May 2020 at 22:49:49 UTC, Felipe wrote: Hi, I develop an interactive terminal fuzzy finder in D with ncurses. Feel free to check it out and contribute. Any feedback is welcome. Cool! Just gave this a quick spin (basic usage without any keyboard shortcuts) - works really intuitively. I hope to remember to use it when it would come in handy. By the way, I really appreciate that you provide ready-to-use snap packages to get automatic updates.. and it should help non-D users ;) Cheers, Fynn Hi Fynn, Good to know that you like it. The idea is to add it to homebrew too. Just have to get some stars/forks before... https://github.com/Homebrew/homebrew-core/pull/54233 * GitHub repository not notable enough (<30 forks, <30 watchers and <75 stars)
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On 05/05/2020 9:05 PM, Robert M. Münch wrote: On 2020-05-04 21:34:27 +, rikki cattermole said: On 05/05/2020 7:26 AM, notna wrote: Maybe you want to add an additional constraint... It would be great if this would result in a tool, scripts or at least a simple-to-follow to-do (say Wiki?!)... so best case we could use this also for the next updates / releases in the future?! The reason we can't just grab a newer copy of the unicode database and throw it into Phobos is because the format was changed. Sure, nevertheless, I think it makes sense to have the reproducibility of the process in mind. Maybe not with a script that lasts for 10 years. But the process, some tools for a specific version, which can be used as inspiration for upcoming changes. Strange, I thought they were in the repo. Okay after looking through his fork of Phobos to see if its lying around somewhere, it looks like we need to hear from Dmitry Olshansky.
Re: D IDE Dexed - v3.9.0
On Sunday, 3 May 2020 at 18:40:37 UTC, notna wrote: On Saturday, 25 April 2020 at 06:55:19 UTC, Basile B. wrote: Despite of the mini drama last year I've continued developping dexed. The changelog since last announce here is a bit long, check https://gitlab.com/basile.b/dexed/-/releases for more information and get the releases (linux only). On Win10 64Bit, after compiling as described in https://basile.b.gitlab.io/dexed/build.html, I have a "dexed.exe" but if I run it, I get "couldn't find dexed-d.dll" ... Can you give a try again after pulling latest changes ? Actually the library indicated as missing was build by calling bash which obviously could not work on Windows. I have pushed a change that replaces this by a direct call to dub since the script was essentially used to "cd" and that's not required as dub has "--root"
Re: Luneta: terminal fuzzy finder
On Tuesday, 5 May 2020 at 07:31:18 UTC, Panke wrote: On Monday, 4 May 2020 at 22:49:49 UTC, Felipe wrote: Hi, I develop an interactive terminal fuzzy finder in D with ncurses. Feel free to check it out and contribute. Any feedback is welcome. Thanks, Felipe [1] https://github.com/fbeline/luneta [2] https://code.dlang.org/packages/luneta [3] https://code.dlang.org/packages/fuzzyd What's the difference to fzf? Seems like this is being discussed here: https://github.com/fbeline/luneta/issues/28
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On 2020-05-04 21:34:27 +, rikki cattermole said: On 05/05/2020 7:26 AM, notna wrote: Maybe you want to add an additional constraint... It would be great if this would result in a tool, scripts or at least a simple-to-follow to-do (say Wiki?!)... so best case we could use this also for the next updates / releases in the future?! The reason we can't just grab a newer copy of the unicode database and throw it into Phobos is because the format was changed. Sure, nevertheless, I think it makes sense to have the reproducibility of the process in mind. Maybe not with a script that lasts for 10 years. But the process, some tools for a specific version, which can be used as inspiration for upcoming changes. IMO it makes a lot of sense for D to keep up close with the unicode development. -- Robert M. Münch http://www.saphirion.com smarter | better | faster
Re: $750 Bounty: Issue 16416 - Phobos std.uni out of date (should be updated to latest Unicode standard)
On 2020-05-04 21:14:49 +, welkam said: If changes to phobos do not bring breaking changes then I dont see how update to std.uni might not be merged Well, but that's a weak statement for an invest. If unicode is developing in a way that results in breaking changes, what to do? Never update? Doesn't make sense... So, breaking-changes because unicode requires these, have to be taken IMO. -- Robert M. Münch http://www.saphirion.com smarter | better | faster
Re: Luneta: terminal fuzzy finder
On Monday, 4 May 2020 at 22:49:49 UTC, Felipe wrote: Hi, I develop an interactive terminal fuzzy finder in D with ncurses. Feel free to check it out and contribute. Any feedback is welcome. Thanks, Felipe [1] https://github.com/fbeline/luneta [2] https://code.dlang.org/packages/luneta [3] https://code.dlang.org/packages/fuzzyd What's the difference to fzf?
Re: Luneta: terminal fuzzy finder
On Monday, 4 May 2020 at 22:49:49 UTC, Felipe wrote: Hi, I develop an interactive terminal fuzzy finder in D with ncurses. Feel free to check it out and contribute. Any feedback is welcome. Cool! Just gave this a quick spin (basic usage without any keyboard shortcuts) - works really intuitively. I hope to remember to use it when it would come in handy. By the way, I really appreciate that you provide ready-to-use snap packages to get automatic updates.. and it should help non-D users ;) Cheers, Fynn
