[yalagadapavankumar]

Add C++ std::chrono::time_point constructors in Rust using overload! macro.

• Default constructor: Creates time point at the clock's epoch.
• Constructor from milliseconds: Creates time point from duration in milliseconds.
• Converting constructor: Creates time point from another time point that uses seconds.

1. Write Rust wrappers for that C++ type, for 3-5 different overloaded method names:
   • Create a new file named after your type in overloading-macros/cpp-overload-test/src/stdcpp
   • Wrap constructors first, writing tests to make sure the correct constructor is called
   • Explain any potential compatibility issues in a Limitations doc section
   • Explain usability issues in an Ergonomics doc section
   • Check that you have implemented all the overloads for each method name, or documented why you can't
   • Push your changes and wait for a review
2. Add a separate example with some failing overloads
   • Create a new file named after your type in overloading-macros/cpp-overload-test/examples
   • Wrap accessor/modifier methods
   • Explain how they fail in an Incompatibilities doc section
   • Explain how the overload failures could be resolved in a Workarounds doc section
   • Optional: If there's a C++ feature with no equivalent in Rust, explain that in an Inexpressible Overloads doc section
   • Push your changes and wait for a review
3. Update the overload macro compatibility table Markdown doc
   • If you haven't checked some kinds of overloads, put a ？in those squares
   • Push your changes and wait for a review

[teor2345]

for the October round, and as far as I can see, they lead to the October channels.

this is the link representing as text which is not for October channel, which is exits in all 3 rust projects, for this project Extend Rust stdlib custom allocator support, they didn't provide zulip properly, so people believe this text is zulip channel for this project.

This is now fixed, and if people accidentally introduce themselves somewhere else, someone from the community will move their post to the right channel.

[teor2345]

Almost there, just need to tweak it to match the C++ overloads a bit more closely.

[teor2345]

Thanks, this looks good, let's move on to stage 2 of this task, using the instructions in the PR description.

Please create a new file with examples of failing overloads, the instructions for creating the stderr file are here:

overloading-macros/.github/workflows/check.yml

Lines 207 to 208 in 3e009c3

	# Or just do `cargo build --package cpp-overload-test --example NAME > cpp-overload-test/examples/NAME.stderr 2>&1`
	# and delete the cargo Updating/Download*/Compiling logs.

[teor2345]

Just a reminder to move on to steps 2 & 3 in the PR description, and make sure they are up to date with your latest code changes.

Applications must be submitted to Outreachy by Monday 9 November, please include this PR and any other Rust PRs you've done in that time.

[teor2345]

This is mostly fine, just need to do code formatting.

Please move on to step 3, summarising the results of the analysis.

[teor2345]

Just need to fix a few things, let me know if you need help with this

[teor2345]

Just going to tweak the whitespace here, then merge

[teor2345]

Just reminding you that the Outreachy final application deadline is this Monday 9 November. You can include any Rust PR or ticket work you've done, it doesn't have to be merged (or reviewed) yet.

Please submit a final application on the Outreachy website before Monday. The exact deadline is 4pm UTC, but it is better to submit early. You can edit your submitted application up until the deadline (and you can keep working on PRs after the deadline).