This group is intended for discussions of coding and design competitions held by Telegram. Please use English. See @contest for information. For discussions in Russian, please use @contests_ru https://t.me/contests/51172
I hope today they say something about that ... I know it's not easy for them but I know that is possible too 😢
Читать полностью…@maximm_bsi this group is for contests organized by Telegram, please contact support by going to Settings > Ask a question
if you're searching for help with other things, this isn't support chat
and please stop reposting messages here after they get deleted.
IOS was supposed to be posted ig, but im not sure
(oh it is from 2024 lol)
if I'll change it to single chars, then my result for the given input looks like
*<b data-markdown="*">bold _<i data-markdown="_">italic bold ~<s data-markdown="~~">italic bold strikethrough ||<span style="filter: blur(2px)" data-markdown="||">italic bold strikethrough spoiler</span>||</s>~ __<u data-markdown="__">underline italic bold</u>__</i>_ bold</b>*Читать полностью…
No, I made it double **, double __ and so on. I think using single chars for that gives a huge room for mistakes
Читать полностью…Nice one,
would that pass this one?
from here: https://core.telegram.org/bots/api#markdownv2-style
I think this is a simple testcase that we can use maybe
*bold _italic bold ~italic bold strikethrough ||italic bold strikethrough spoiler||~ __underline italic bold___ bold*
<b>bold <i>italic bold <s>italic bold strikethrough <span class="tg-spoiler">italic bold strikethrough spoiler</span></s> <u>underline italic bold</u></i> bold</b>Читать полностью…
I think it's a difficult situation. For me, I feel a bit sorry for Cool Ram, who probably made the second fastest solution but had 8 fails over 11841 tests. Maybe it's just a small mistake that could be corrected in less than an hour while it probably took many hours to him to optimize the code. The more you optimize, the more you increase your chances to introduce bugs. Penalizing too much test fails could discourage trying big optimizations of the code.
Читать полностью…Thank you for comprehensive scoreboard and explanation, that answers most possible questions 👍
Читать полностью…And really it's easy to find which one of them tried other solutions 👍
Читать полностью…I hope they could do that, let's see what they decide :(
Читать полностью…however it's not included in contest explaination ...
but we understand, thanks.
We are attaching a breakdown of the Final Results for each submission.
1. Final Results:
Initially, for preliminary testing published on contest.com, we ran each test in a separate process. This allowed us to fully evaluate even solutions that crashed or hung on specific tests. However, this method disrupted many participants' performance optimizations and introduced substantial noise into the results.
Therefore, for the final evaluation, we executed all tests in a single process using a grader closely resembling the provided contest-grader.cpp. Consequently, solutions that crashed or hung on any test received a final score of 0.
2. Post-Contest Corrections:
After announcing preliminary results, several participants submitted bug fixes via comments on contest.com. Although we typically do not accept post-contest corrections, one corrected solution turned out to be significantly faster than any solution submitted during the contest. As an exception, we decided to evaluate all corrected submissions and include them in the final standings. To maintain fairness, these late submissions incurred a 20% penalty on the prize amounts awarded.
Can you share some resources so i can learn more
Читать полностью…For those who is interested, here is my attempt to implement the input field with the requested features (took me about a week by itself, so it's not a part of my submission). Features covered:
- Custom Undo / Redo history (no document.execCommand used), edit history is implemented using CacheStorage (virtually unlimited storage).
- Supports markdown (bold, strikethroug, _italic_, underline, spoiler)
- Markdown parsing done asynchronously using Web worker (so it will never freeze or block UI).
- Source code can fit one screen, so it's not rocket science and simple to understand
I thought like, okay I couldn't finish it before deadline, however won't be bad to share it with the community:
https://github.com/angrycoding/react-contenteditable-input
DEMO: https://angrycoding.github.io/react-contenteditable-input/
Will you post updated testing results for anyone with post-deadline patches? I.e. Classy Sloth (winner) only has the original time with a lot of failed tests
Читать полностью…Will the js contest‘s result announced this week?
Читать полностью…currently there are none, follow @contest to learn as soon as new one shows up
Читать полностью…Yoo what contests are currently open for devs?👐🏾
Читать полностью…nice to see that they accepted your correction.
and really appreciate winners!
but as another person said it's good idea to share penalty between others that tried some solutions and passed all tests ...
basically the winners were decided in order of min(rank_time, rank_cpu)
Читать полностью…this is really good idea if it be possible 👌🏽
Читать полностью…at least distrubute penalty prize between other users that uploaded their tried solutions and passed all tests 😒 prevent wasting time :(
and they could participate in next contest :(
Beginners are not capable enough to come with performant and optimized solutions.
Читать полностью…It’s surprising to see someone with so many failures in first place, especially when the top priority was explicitly stated to be passing tests. Additionally, I documented numerous approaches I tried (like you), and I could have submitted further patches after the deadline, as some winners did(what's deadline for? when you dont allow?!). This raises questions about the fairness of the contest
Читать полностью…