RazgrizHsu

RazgrizHsu

Hi, all,

i’m trying compare with timex variables,
but i don’t know why this code work like that..


dts = Timex.parse!( "2019-01-01T00:00:00.000Z", "{ISO:Extended:Z}" )
now = Timex.parse!( "2019-01-01T00:00:00.100Z", "{ISO:Extended:Z}" )

dt = Timex.shift( dts, seconds: 5 )
	
if ( dt <= now ) do
	raise ( "why? dt already shift seconds... dt[#{ inspect dt }] now[#{ inspect now }]" )
else
	:ok
end

I thought that such a comparison should be the opposite result…

anyone can help me to understand this? thanks

Showing Posts 5 to 1

RazgrizHsu

RazgrizHsu OP

This is indeed a very good suggestion, thank you :smiley:

NobbZ

NobbZ

I tend to always use the regular comparison operators against 0.

Timex.compare(start, end) <= 0

This does match semantics very well.

RazgrizHsu

RazgrizHsu OP

okay thank you guys,

so i need change my code to

#if ( dt <= now ) do
#instead by
compared = Timex.compare( dt, now )
if ( compared == 0 || compared == -1 ) do

right?

@kip thank you for explanation :smiley:

i was wrong a test to make sure my project working… but seem not work :smile:

test "compare with operations" do
	
	#equal
	a = Timex.parse!( "2017-01-01T01:00:00.751Z", "{ISO:Extended:Z}" )
	b = Timex.parse!( "2017-01-01T01:00:00.751Z", "{ISO:Extended:Z}" )
	assert( a == b )
	assert( ( a < b ) == false )
	assert( ( a > b ) == false )
	assert( ( a <= b ) == true )
	assert( ( a >= b ) == true )
	
	#offset 1ms
	a = Timex.parse!( "2017-01-01T01:00:00.750Z", "{ISO:Extended:Z}" )
	b = Timex.parse!( "2017-01-01T01:00:00.751Z", "{ISO:Extended:Z}" )
	assert( ( a == b ) == false )
	assert( ( a < b )  == true )
	assert( ( a > b )  == false )
	assert( ( a <= b ) == true )
	assert( ( a >= b ) == false )
	
	#offset 5secs
	a = Timex.parse!( "2019-01-01T00:00:00.000Z", "{ISO:Extended:Z}" )
	a = Timex.parse!( "2019-01-01T00:00:05.000Z", "{ISO:Extended:Z}" )
	assert( ( a == b ) == false )
	assert( ( a < b )  == true )
	assert( ( a > b )  == false )
	assert( ( a <= b ) == true )
	assert( ( a >= b ) == false )
end

I need to add this paragraph to remind me of myself :smile:

#Tips: the operation compare will fail with milliseconds, instead by Timex.compare
a = Timex.parse!( "2019-01-01T00:00:05.000Z", "{ISO:Extended:Z}" )
b = Timex.parse!( "2019-01-01T00:00:00.100Z", "{ISO:Extended:Z}" )

assert( ( a == b ) == false )
assert( ( a <= b ) == true )	# it's wrong, normally it's should be false

thanks guys :slight_smile:

kip

kip

ex_cldr Core Team

The built in comparison operators aren’t the right tool for this job. You probably want to use Timex.compare/3.

For an explanation of why this is the case you might find this useful. Especially this quote:

Maps are compared by size, then by keys in ascending term order, then by values in key order. In the specific case of maps’ key ordering, integers are always considered to be less than floats.

NobbZ

NobbZ

You need to use Timex.compare/2/3 instead of Kernel.<=/2.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews